The tooling around upgrading has definitely gotten a lot better, though if you’re carrying around a relatively older codebase there’s a potentially thorny deprecation coming up in the future
I would say that for most frameworks/libraries. Keeping up with the Joneses is hard and Ember has taken particular care in both pioneering new ideas and bringing in new ideas from other domains and libraries. I'm just grateful that all the apps I have worked on since 1.13 have not been painless to upgrade, but have been totally worth it. Over the long term, stability, ergonomics and performance have been improving steadily and there has been a nice community around to help. That is about all I can ask for. Continuous improvement + nice people == recipe for software success over the long term.
Comments
The upgrades in the 2.x range were pretty demoralizing for myself and my team. Have they gotten any better?
The tooling around upgrading has definitely gotten a lot better, though if you’re carrying around a relatively older codebase there’s a potentially thorny deprecation coming up in the future
It is usually automatic, with running one command: https://yoember.com/emberjs/how-to-keep-your-ember-js-projec...
In theory yes, but for larger apps, especially those that use addons, definitely not.
The 2.x were the reason I many people I know dropped it.
I would say that for most frameworks/libraries. Keeping up with the Joneses is hard and Ember has taken particular care in both pioneering new ideas and bringing in new ideas from other domains and libraries. I'm just grateful that all the apps I have worked on since 1.13 have not been painless to upgrade, but have been totally worth it. Over the long term, stability, ergonomics and performance have been improving steadily and there has been a nice community around to help. That is about all I can ask for. Continuous improvement + nice people == recipe for software success over the long term.