So do screen resolutions, and when you include images and video in the website size it seems reasonable they'll be getting bigger.
I have a 14+ year old laptop with a WUXGA (1920x1200) screen. That is similar to FHD but 16:10 not 16:9 so its a bit higher that FHD (which is the standard today).
Web devs should be building sites that deliver the best assets for the users device, but they often don't and just send the giant images and let the users browser scale them down to fit.
Hence bigger websites.
You mean 32MB 2040?
web3.js is a super bloated library and will be added more frequently unless a team does a more optimal version from scratch
ready contract data from the nearest node is a pretty benign and common aspect of what web3 inclusion in a site does. just accessing variables and constants in a cloud data store that can be read for free.
The issue with the lib is its non-treeshakeable nature. It should be rewritten using ES6 modules.
That doesn't seem so hard, unless I'm missing something. Certainly shouldn't need a full rewrite from scratch.
My point is, it's not just about bloat and having too many features (which are very hard problems to fix); it's often low-hanging fruit that isn't being picked.