the fact that everyone thinks we could "just swap Broccoli for Webpack" is more or less the point.
-
-
Replying to @wycats @mcardleliam and
Broccoli is a build pipeline that takes input directories and produces an output directory. 1/
1 reply 4 retweets 3 likes -
Replying to @wycats @mcardleliam and
Webpack is a tool that builds your app using JS module semantics. They're not at the same layer of 2/
1 reply 4 retweets 3 likes -
Replying to @wycats @mcardleliam and
abstraction. Webpack could be built on Broccoli, but not the other way around. 3/
1 reply 4 retweets 2 likes -
Replying to @wycats @mcardleliam and
"You guys should just ditch Broccoli for Webpack" reminds me of "you guys should just adopt React as your 4/
1 reply 2 retweets 1 like -
Replying to @wycats @mcardleliam and
view layer under the hood" -- we actually considered it, but I'm real glad we proceeded with Glimmer, and I 5/
1 reply 2 retweets 3 likes -
Replying to @wycats @mcardleliam and
think the ecosystem is better off for us doing it. I think the JS ecosystem can tolerate a couple of 6/
1 reply 2 retweets 5 likes -
Replying to @wycats @mcardleliam and
different build tools, giving different models space to explore and learn from each other. That doesn't 7/
1 reply 2 retweets 5 likes -
Replying to @wycats @mcardleliam and
mean 50 slightly different tools is good, but a handful of different areas of exploration is great. 8/8
2 replies 2 retweets 9 likes -
Replying to @wycats @mcardleliam and
now that I understand how broccoli works webpack could bundle broccoli output, but not work on top
1 reply 0 retweets 0 likes
Broccoli is just a description for how to go from trees -> tree. Webpack is a transform.
-
-
Replying to @wycats @TheLarkInn and
Do you want rants? Because that's how people get rants.pic.twitter.com/Oo9b76Kwp4
1 reply 0 retweets 3 likes - 1 more reply
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.