Every kind of software has started using package managers that bring in code recursively and end up creating lots of redundant functions that make cache misses more likely. Also file sizes gigantic.

NPM is by far the worst offender here, which extra sucks because javascript is the language that gets shipped over the network for like every fucking webpage.

This is also why Marxists.org is unironically peak web design

Edit: forgot to rant about this: for the uninitiated, NPM "resolves" dependency conflicts by installing multiple versions of the same package. Say your project requires you to install the package axios and the package react. If axios depends on the package left-pad at version 4.20.0 and react depends on the package left-pad at 6.9.0, NPM will install two copies of left-pad, one at version. 4.20.0 and one at 6.9.0.

Websites often use hundreds of packages, and packages each tend to have at least a handful of dependencies (and can sometimes also have hundreds). Sometimes dependencies include a shitload of extra data, and the developers writing and adding these dependencies tend not to care about or understand the build and deploy process (or often aren't given enough time to care about it) and don't really try to optimize the amount of space these packages take up. I've had to spend weeks trimming down one application's node_modules file because it kept breaking the build server, that shit was several GB when I started and still like 400 fuckin MB after I sunk a bunch of hours into fixing it