[nercury]

I would argue that the bloat comes when the performance impact is not perceivable compared to the development time.

The easiest optimization strategy is just to load it all up into the memory. Compare that to other strategy like catching partial file data, and it's obvious why the simpler solution is often chosen.

Another example that comes to mind is vector art vs baked art. You can render nice icons as vector art. Or you could ship perfect baked icons for all possible size variations. There are clear trade-offs here. One of them wastes more CPU cycles, and another one wastes storage space and download time.

[maccard]

Load what all up into memory? That doesn't solve the N+1 problem, or chained async methods. It causes caching issues (what if something else changes the files you're working with?).