3 ms·
You paint a very utopian picture, but that's just not how it works in the real world. Throw a dart at a map of both startups and large companies, and you'll fin
by bryans 5y ago
You paint a very utopian picture, but that's just not how it works in the real world. Throw a dart at a map of both startups and large companies, and you'll find full dependencies included in otherwise small scripts. Sometimes those dependencies will even get included in multiple files, because Google convinced a generation of developers that "above the fold" was the most important thing in the history of the web -- even though Google themselves abandoned the concept almost immediately.
The focus these days is on tooling instead of code, and that has resulted in fragile infrastructures serving massive amounts of code in order to provide relatively little functionality for the end user -- all because we'd rather use some extra cheap electricity than actually learn how to write highly-performant code. I'm really not sure why you view that as a positive.
- faeyanpiraat 5y agoI don’t get how including dependencies multiple times is related to “above the fold”, could you clarify?
- bryans 5y agoThe method that most frameworks and developers use to accomplish any form of "above the fold" reactivity, is to chunk portions of a page, where each of those chunks gets its own renderer, of sorts, and whatever other dependencies that particular section of code might need. It's incredibly easy to either accidentally include large dependencies within each chunk, or repeat a dependency across multiple chunks, or to accept it as a problem to throw money at -- because it's far cheaper to expand infrastructure than to increase hiring, and way more palatable to the financial team when the buck just gets passed on to the consumer. For some reason, it has never really bothered project managers that just "throwing money at it" is entirely antithetical to the point of "above the fold."