|
|
|
|
|
by atonse
19 days ago
|
|
I loved ember for years. Even attended EmberConf in portland around 2015. In fact, I'm just weeks away from retiring my last ember codebase that was in production and worked great for a decade (but I haven't updated in 5 years, since I was unable to keep up with all the changes). But after years of the community dying the most slow and boring of deaths, and having an absolute nightmare needing to hire Ember consultants, I really soured on it. It is the main reason I completely stick to the boring mainstream (like react) now, so I'm never again stuck between "nobody knows Ember" and "this one consultant is charging $28k a month cuz I'm competing with LinkedIn, Netflix, and Apple" and then am stuck with them implementing engines for fun and then I don't have the time to undo it months later - all left me wanting to flee. Basically, left it for non-technical reasons, just practical "literally nobody except billion dollar companies use this, I've painted myself into a corner" reasons. But I do have fond memories of building things with it, personally. |
|
Since then I realized I’ll never require a react/vue/angular/ember/svelte/etc experience, just go for good JavaScript developers with frontend experience, framework doesn’t matter.
Took them a week or two to understand the Ember patterns that’s it.
I think we overcomplicate, all these frameworks are just slightly different ways how to build web apps, the core patterns are the same. Anyone experienced can pick any of these frameworks in matter of days or weeks.
Same on the backend, great if you’ve have experience with any of the express/hapi/koa/nest/fastify/hono, but if you don’t have experience with the one we use, it’s still fine. Hire good engineers, not good “framework” engineers.