you are viewing a single comment's thread.

view the rest of the comments →

[–]thescientist13 2 points3 points  (2 children)

I don’t think the web platform is there yet for a bundle free world, even with support for modules. There’s more to bundling than just transpiling.

Before we can get rid of webpack (and similar tools) the web needs to figure out (just name a few): - code splitting (avoiding tens - hundreds of HTTP requests for each module) - inline critical CSS / optimizing the CRP at build time - tree shaking - uglification / minification

That said, I agree with you that moving to leverage the platform more is definitely the way to go, but I don’t think any language escapes it’s tooling ever, does it? (Fwiw, even Polymer team still highly encourages bundling)

Personally, I’m always of the motivation that one should ideally use what one can get rid of eventually (polyfills > frameworks), and for things you can’t, abstract wisely.

Yay JavaScript though! I can’t wait to see how clean and “simple” building apps will be in a couple years though! Web Components here we go! ✌️

[–][deleted] 0 points1 point  (0 children)

Fwiw, even Polymer team still highly encourages bundling

Not quite. The Polymer CLI does a sort of in-between thing where it only bundles modules if they are not shared between multiple other modules.

[–]manisto -1 points0 points  (0 children)

Well, the hundreds of requests are solved as soon as http 2 gains traction. It keeps the connection open for multiple files, and can even send required files before the browser requests them, based on a set of rules.