ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
83% Positive
Analyzed from 747 words in the discussion.
Trending Topics
#ember#button#still#backbone#years#framework#same#frontend#frameworks#template

Discussion (20 Comments)Read Original on HackerNews
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.
And Apple is still using Ember? I seems to remember they moved off it some years ago.
Ember on frontend is what Rails is on backend: less fashionable, opinionated, mature, and still useful when you value long-term app consistency over ecosystem hype and new JS framework of the month.
I got news for you: that hasn't been the case in 10 yrs now. It's no longer 2010 in case you didn't notice.
Seriously, react, emberjs angular, vuejs etc - they're all essentially the same age at this point.
We need more LTS versions of dev tools like emberjs, django, node etc. And am a fan of their RFC process as well. It looks like this is the framework you use if you want to incrementally improve stuff without having to go through radical shifts between versions.
It turns out they didn't use any of those and didn't ask questions about them in the interview. :) After a year or so they did start using Angular though.
Anyway, I did end up playing with ember and backbone around that time. Cool to see it's still developed.