3 ms·
It's dumb, because most of those little shim libraries are things that would be part of the language's core library in a less shitty language. Then when you ha
by douche 11y ago
It's dumb, because most of those little shim libraries are things that would be part of the language's core library in a less shitty language.
Then when you have all these little libraries, you've got to go down the bundling path (and navigate the bewildering array of almost but not quite the same tools), because making 47 HTTP GETs to grab < 1KB JS files is slow. Theoretically, some of those might be cached, but the churn-rate means that virtually no one will have the exact version of a library that you require pre-cached in their browser.
- deleted 11y ago[deleted]
- klibertp 11y agoThere's nothing wrong with "going down the bundling path". Virtually every compiled language does this via a linker. Java's jars are another example. You have at least 3-4 different tools for doing this in Python. In short: "bundling" is just JS catching up to how software was deployed for ages. Source maps are equivalent to leaving debugging symbols in the binary, only without performance costs.
- deleted 11y ago[deleted]
- buchanaf 11y ago'It's dumb, because most of those little shim libraries are things that would be part of the language's core library in a less shitty language.' I think you are mistaking the language with the browser.