I'm not sure I've got the energy to write a blog about it but one of my wishes for #EmberJS2018 would be to find some way to de-stigmatize the competition.
-
-
The problem is that webpack has been innovating rapidly while we are left reimplementing that stuff with far fewer contributors. We’re going to get left in the dust
-
Can you, please, explain more which exactly features of webpack you are missing in ember world?
-
Imo this is the wrong perspective. I miss the general webpack ecosystem with tons of contributors, docs etc. No good reason for ember to try to duplicate features.
-
Sorry but I cant buy it. I don’t miss general webpack ecosystem because I don’t need it.
-
How much dead code does your app ship? :) Also how long does it take to get interactive?
-
The Ember story is focused on a stable API that conventionally compiles apps *and* addons. In general, the tradeoff is that Ember takes longer to get features, but they work for apps and addons built 2-3 years ago, and the ecosystem moves forward together.
-
The hard work doesn't come from duplicating features, but from managing upgrades &maintaining conventions. We may end up adopting Webpack or Rollup in Ember, but the bulk of the work would still be maintaining the public API and designing an ecosystem-wide migration strategy.
-
libkit (a conventional Ember CLI-based toolkit for building Typescript libraries that I maintain with
@chancancode) uses Webpack for building tests, and Glimmer.js uses rollup for building apps. Broccoli isn't a blocker for using these tools (it's a glue layer), but ... - 3 more replies
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.
