it's the ones who rave "microoptimizations matter goddamn it!" who will try to shave 150ms off the "send money" screen of the banking app and not notice that the app takes up 750MB of storage.
Or spend 2 days shaving off 150ms that no one asked for when we have much more pressing features. I don't care if the button is faster if the action it kicks off doesn't work. The road to hell and all of that...
But it's usually the other way around? Lightweight usually means faster. It's takes less bandwidth, it can be cached more efficiently at network edges and in CPU cache.
There exist tradeoffs that might make bulkier applications worth it, like faster and cheaper development I guess.
It's kind of funny because I'm not 100% sure which one you are talking about. I assume it's the time, storage be damned. I agree that's probably what users will say but in that world (picking speed over storage) we will see this exact same article posted with a stronger focus on the app size (the post does make at least 1 mention of app size).
