Ember's build pipeline is focused on enabling Ember's conventions. That's why Ember addons are so powerful and plug-and-play, and why it takes longer to implement certain features: Adding a feature to Ember's build pipeline means bringing along add-ons.
-
-
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 -
-
-
You don't need to bring the whole ecosystem, just the active parts. I'd even say it's *therapeutic* to kill compatibility of older addons. And the cost of compat seems to be that every ember user spends more developer-hours working around still-unfinished migrations/upgrades
-
For every hour I save thanks to ember conventions I lose another to the outdated tooling, the isolated ecosystem, or a feature/bugfix that breaks compat and hasn't shipped in 2-3 years It's disheartening to say the least
-
All I've seen in this thread is defenses for *why* ember is stuck in 2016 and pushback on every suggestion for how we can rejoin the JS ecosystem. Defending the status quo isn't productive, but perhaps twitter isn't a good place for a discussion like this
-
You *might* be asking for the impossible? You mention Rails sometimes breaks compat to move faster but IMO even Rails is "stuck" in the past in some/many aspects (I mean Jesus how late was ActionCable to the party)
-
"All I've seen in this thread is defenses for *why* ember is stuck in 2016", sure but this is like any other situation with a good-fast-cheap triangle, or CAP theorem, where you state your goals/philosophies at the knowing expense of others.
-
(all this keeping in mind that I started this thread with criticism of myself and others who dismiss the competition *because* it's not the convention that Ember has chosen, which I still think is a real problem/tendency/risk)
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.