I think the issue though is that for better or worse there is a clear signal that The Core Team Has Agreed that JSONAPI is The Winner, and that the most GraphQL fans can hope for is that _some_ of the functionality of GraphQL will eventually translate to future JSONAPI features..
-
-
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 ... -
(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.