which is unfortunate. If we could standardize / work on improving the same tools, imagine what could be achieved.
-
-
I'm not saying it is as easy as that. Rather, imagining the possibilities if dev tools were common among frameworks
-
and my comments are no attack on ember, I am a big user and appreciate it all.
End of conversation
New conversation -
-
-
Broccoli is a build pipeline that takes input directories and produces an output directory. 1/
-
Webpack is a tool that builds your app using JS module semantics. They're not at the same layer of 2/
-
abstraction. Webpack could be built on Broccoli, but not the other way around. 3/
-
"You guys should just ditch Broccoli for Webpack" reminds me of "you guys should just adopt React as your 4/
-
view layer under the hood" -- we actually considered it, but I'm real glad we proceeded with Glimmer, and I 5/
-
think the ecosystem is better off for us doing it. I think the JS ecosystem can tolerate a couple of 6/
-
different build tools, giving different models space to explore and learn from each other. That doesn't 7/
-
mean 50 slightly different tools is good, but a handful of different areas of exploration is great. 8/8
- 13 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.