4 ms·
There's a reason why a lot of those libraries and tools are used though. Webpack bundles are used to strip down multiple JS files and libraries into a single bu
by applecrazy 7y ago
There's a reason why a lot of those libraries and tools are used though. Webpack bundles are used to strip down multiple JS files and libraries into a single bundle that contains only what is needed to run a particular application. Libraries like React serve a purpose too, particularly when you're building large applications that need to be maintained by many people all at once, or when you need insane compatibility (e.g. IE 11, the old Edge, etc.)
Is there a need for these tools all the time? No. But are there valid use cases? Absolutely yes.
- rimliu 7y agoAlas, the reason #1 these tools are used is cargo-culting.
- efdee 7y agoIE11 is "insane compatibility" now? rants about having to support IE6
- applecrazy 7y agoWell, I don’t write JS for a living, so I haven’t really needed to support anything other than relatively modern browsers.
- 6510 7y agoRight, its so funny! This is why I cant/wont/refuse to find a job of this type. I can write JS just fine. In employment I would have to glue bloated libraries (which takes me forever!) and then wait for tools to purge the unwanted garbage from the creation. The end result is slow and I feel clueless what is actually going on. Of course this also means I'm impossible to work with which only adds to the joke. I do have a sense of humor about it. https://jsfiddle.net/gaby_de_wilde/c8bhcatj/ https://jsfiddle.net/gaby_de_wilde/c8bhcatj/
- austincheney 7y agoYeah it’s really frustrating. My metric of the moment is total NPM package count that comprises a project. Since Angular, out of the box, is greater than 1100 packages I ignore all job postings that mention Angular. I am extremely hesitant whenever I see things like Webpack or Babel.