Similar thing happened with Webpack.. I think the Ember community could have benefited a lot from it. But now it seems unlikely we'll ever use similar tooling from the rest of the community, and we won't benefit from the advances there.
-
-
(not to repeat myself), we prioritize convention over configuration, stable updates, and bringing the whole ecosystem along. There's a ton of active work with good progress towards exposing a generalized packaging hook (to allow webpack, parcel and rollup for last-mile bundling)
-
and a ton of active work to bring code splitting and tree shaking to Ember apps by default. A ton of *that* work is internals updates to eliminate implicit dependencies and depend on modules more. And work to allow our DI to work better with tree module-based tree-shaking.
-
It's gonna be awesome! Ultimately, Ember is about building a community that values doing this work together, despite the fact that it means it takes longer to get the first support out of the gate. If you're into that, Ember may be your jam


End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.