embroider

I agree there have been some mistakes (difficult to design the perfect framework on your first attempt), but overall we're quite happy with Ember. - Embroider is actually 1.0 now and quite usable (https://github.com/embroider-build/embroider). - Agree with Ember Data and nested resources, that's still needlessly complicated. Same with lack of wildcard in the router/URL. There are still things Ember needs to fix, for example removing controllers and improve Ember Data. But overall I think there is a good future ahead for Ember.

You're not alone! The Ember core team broadly agrees with this goal. With Octane, we focused on landing broad ergonomic improvements in a compatible release of Ember. At the same time, we've been working on updating the way that Ember builds JavaScript so that it can make better use of tree shaking and code splitting tools in modern bundlers. That project is called Embroider[1] and it currently builds substantial Ember codebases. Wrapping up Embroider and shipping it by default is a substantial part of the work we have planned for 2020[2]. Also, now that Octane idioms fully replace the need for Ember's original object model (designed in 2012!), I would expect it to become an optional feature, meant to be used primarily as a transition path. When combined with tree shaking, that should substantially change the default byte size of Ember. I