And the addon API doesn't even have that direct of a relationship to Broccoli, in the same way that the Ember component lifecycle makes sense even if it wasn't generating DOM at the end.
-
-
Yeah I won't fault the addon API at all. I love it, I just have gripes with the feeling that ember is constantly reinventing things that it seems (1) everybody else coalesced on a solution for and (2) nobody else can benefit from our reinvention
1 reply 0 retweets 3 likes -
It feels like ember picks a tool early in the race and when everybody else hits the same problem and coalesces around an alternative, we stubbornly keep our existing tool due to sunk costs
1 reply 0 retweets 2 likes -
… And this results in a weak ecosystem because I can't borrow tools directly from other ecosystems, just ideas. And ideas are frankly near-worthless when I'm trying to build a product quickly
3 replies 0 retweets 2 likes -
From the perspective of quickly shipping your product, what would you say are the biggest things from Webpack missing in Ember that are slowing you down?
4 replies 0 retweets 1 like -
I totally get the frustration of wanting to do something in your app and feeling held back by your tools.
1 reply 0 retweets 2 likes -
Emma the problem is that for Ember to go full webpack the "right way" they need to use modules top down, which is (last I worked with the cli team and ember team) is a pretty tough feat. Glimmer is promises of the future however. Just know we actively want to have webpack+ember
1 reply 0 retweets 1 like -
Replying to @TheLarkInn @wycats and
Ember makes a very valuable yet discrete tradeoff: Compat at the cost of being held back a little, but with a much more stable moving ecosystem.
1 reply 1 retweet 3 likes -
Replying to @TheLarkInn @wycats and
Dependency Injection would need (or should in my subjective opinion) be repalced with ESM, and that's a whole archetectural rewrite almost.
3 replies 0 retweets 2 likes -
Replying to @TheLarkInn @wycats and
Things like ember-islands, engines would/could (unless just behind the scenes changes) be completely rewritten. Lazy loading add-ons is kind of a cool opportunity, and I'm interested in hearing what Katz n Frands are going to do there!
1 reply 0 retweets 1 like
Largely behind-the-scenes changes is right (and most of it is already under-way). Lazy-loading by route, engine or addon in a transparent way is all possible, and what we're expecting Ember's conventional nature to buy us.
-
-
And component registration! Anywhere components are registered, use modules to do it, and any where that takes a Component takes a ()=>Promise<Component> this way stuff in handlebars if statements only resolve the promise if conditional is true, etc.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.