|
|
|
|
|
|
by jondubois
3153 days ago
|
|
|
It's a great project but I don't understand why they need so much money for the future. It's a bundling tool. Wasn't it supposed to be a transition project? Won't Webpack get replaced by simpler things like ES6 module import and HTTP2 push? It was the same thing with CoffeeScript; it inspired some neat features in JavaScript but it has made itself obsolete; the ecosystem caught up. It fulfilled its purpose nonetheless. Webpack would probably have benefited more from this funding a few years ago. |
|
|
Based on what I've read, sending a few bundled chunks instead of many individual module files will still generally have less overhead. In addition, Webpack's ability to load and transform other file formats like images and styles is something that simply requesting ES modules over HTTP2 can't deal with. Webpack's ability to code-split an application is also important.
Tobias Koppers, the main Webpack developer, wrote an article last year on how Webpack and HTTP2 relate: https://medium.com/webpack/webpack-http-2-7083ec3f3ce6 .
It's also worth noting that Tobias had only been able to work on Webpack intermittently for the last couple years, until this recent funding allowed him to work on it full-time. Tobias has been writing reports on what he's been doing [0]. Also, grants and full-time development is enabling the team to work on projects like integrating WebAssembly support directly into Webpack [1].
[0] https://medium.com/webpack/the-chunk-graph-algorithm-week-26...
[1] https://medium.com/webpack/webpack-freelancing-log-book-week...