There are so many misconceptions about what microservices are or what problems they are trying to solve. Most people don't even experience the problems (yet or ever) they are meant to solve and they go straight to micro. 5 person teams making 5 services to power their product :faceplam:. A relatively simple b2b web application without any serious traffic also does not need microservices to handle its load.
People just read up on whatever seems to be the newest, coolest thing. The issue is that MS articles are usually coming from FAANG/ex-FANNG. These companies are solving problems that 99% of others do not.
As engineers we should be looking for the most effective solutions to a given business problem. Sadly, I see engineers with senior/staff titles just throwing cool tech terms/libs around. Boring tech club ftw
As a CTO, I couldn't agree more. For our internal product, we use 100% boring technologies. The most "modern" you'll find is a React SPA.
I sigh when clients want to go the microservices route for a team of just a few developers. When you want to use NextJs for their tables&forms app. When they choose to use Kubernates instead of a couple EC2 instances.
Don't get me wrong, these technologies are great for us because we can charge more for the wasted human time developing these overengineered solutions. But I always, for my peace of mind, try to talk them out of them. Sometimes works, sometimes doesn't, at the end of the day it's their money.
Oh man, I've been a fan of your app for so long! Have you ever considered an official iOS app? I think it's the only thing that keeps me from leaving Apple Notes.
I might make another iOS app for TaskPaper at some point. But as an individual developer splitting myself across multiple projects and multiple platforms becomes painful pretty quickly.
iPad app with sync and same sort of keyboard shortcuts would be great (and would pay for handsomely). Clearly a lot of effort and intelligence went into TaskMator, but for me it somehow didn't translate the simplicity of TP to a touchscreen interaction.
LayerVault is a great tool if you want to keep your design files version controlled and nicely organized, which is the primary function. They have also introduced a handoff feature (http://layervault.tumblr.com/post/82302518939/introducing-as...) that is somewhat closer to Avocode.
But Avocode aims to be your tool of choice when it comes to designer->developer interaction and VICE VERSA. Many services often forget those developers who must code the same parts over and over again.
Parsing the PSD format is quite a challenge given its "half-open" nature. We've looked at many different libraries out there and basically took the best from each. Now we're also contributing to the open PSD.rb implementation.
We cannot speak for the Parfait team, but we think there are some key differentiators given that their tool is from Adobe. Read Q11 at http://avocode.com/faq.html
I know Sketch is mentioned in the FAQ as something that may come later. But, Sketch is quickly becoming the darling of the web design world, and the development world just hasn't adopted it yet. Want to corner the market? Support Sketch sooner, rather than later. I'm really looking forward to seeing what Avocode can do!
