5 ms·
I mean, we used to all just use jQuery and lodash. Then the cool kids decided that wasn't cool anymore, and every function should be a separate package. I'm su
by thrower123 7y ago
I mean, we used to all just use jQuery and lodash. Then the cool kids decided that wasn't cool anymore, and every function should be a separate package.
I'm sure the wheel will come around again.
- other_herbert 7y agoShow us this, "the wheel"
- other_herbert 7y agoman tough crowd :)... I thought more of you would've gotten the Futurama reference ... Fear of a bot planet.. I think.. edit no, the one with the evolution of robots and such
- whostolemyhat 7y agoThat's because there's no point including an entire library if you only need a few functions. It means that your deployed bundle is much smaller, which means that users don't need to download unused code and waste time/bandwidth (ie a good thing). Tree shaking still isn't that great or widely available, so separate packages mean you can do this manually.
- fhennig 7y agoIf there is a set of standard libraries, wouldn't they be cached in the browser anyways?
- filleduchaos 7y ago> Tree shaking still isn't that great or widely available This sounds like an opinion based on the state of web development a decade ago. In 2020 on the other hand the Google Closure Compiler has been a mature project for years, and even projects not explicitly focused on dead code elimination (bundlers like Webpack and Rollup) do a decently thorough job of cutting out unnecessary code with the right plugins.