4 ms·
Personally, I still have ember apps from 2015 that are now on v3.6 and have had pretty much painless updates. I have used react professionally, but used Ember w
by ricketycricket 8y ago
Personally, I still have ember apps from 2015 that are now on v3.6 and have had pretty much painless updates. I have used react professionally, but used Ember when starting a new app this past fall. I just trust them to keep things stable over time and I don't have the ability or desire to spend a lot of time bikeshedding my setup. It's not glamorous, but I do get a lot done and can keep things working for years.
- aarpmcgee 8y agoThe upgrades in the 2.x range were pretty demoralizing for myself and my team. Have they gotten any better?
- vmware505 8y agoIt is usually automatic, with running one command: https://yoember.com/emberjs/how-to-keep-your-ember-js-project-up-to-date/ https://yoember.com/emberjs/how-to-keep-your-ember-js-projec...
- Macha 8y agoIn theory yes, but for larger apps, especially those that use addons, definitely not.
- Rifu 8y agoThe 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
- k__ 8y agoThe 2.x were the reason I many people I know dropped it.
- snewcomer24 8y agoI 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.