And analytics. And offloading as much computation to the client, because servers are expensive and inefficiency is not an issue if your users are the ones paying for it.
The Samsung shop hands out 1.4mb JSON responses for order tracking, with what I estimate 99% redundant information that is repeated many times in different parts of the structure.
Electron everywhere.
And analytics. And offloading as much computation to the client, because servers are expensive and inefficiency is not an issue if your users are the ones paying for it.
I saw an ad request with an inline 1.4 MB game. Like, you could fit Mario in there.
The Samsung shop hands out 1.4mb JSON responses for order tracking, with what I estimate 99% redundant information that is repeated many times in different parts of the structure.
Web “Apps” are also quite bad. Lots of and lots of stuff we’re downloading and it feels clunky.
Sometimes that’s bad coding, poor optimization, third party libraries, or sometimes just including trackers/ads on the page.
I vaguely recall a recent-ish article that an average web page is 30mb. That’s right, thirty megabytes.
It’s amazing how much faster web browsing becomes when I run PiHole and block most of it.
Suddenly the TV is pretty snappy, and all browsers feel so much smoother.
And I’m sitting here uneasy thinking how the hell I’m going to compress my map data any further so that my entire web app is no bigger than 2 mb. 😥
No, you need to go further: https://512kb.club/
Oh god, I’m not ready for the trauma and the emotional scars… D:
That’s straight up not true. It’s not even remotely close to that.
https://httparchive.org/reports/page-weight
Some devs will include a whole library for one thing instead of trying to learn another way to do that thing.
from * import *A whole library which was meant to to 10 things, but you only use one. And that for x libraries
Nowadays libraries are built with tree-shaking in mind, so when it’s time to deploy the app only the code that’s actually used gets bundled.