"Windows 95 was 30 MB" is such an ignorant, obnoxious, trite take. a triple buffered framebuffer (which you want for smooth scrolling) for my 4K display is 70 MB in *pixels alone*. Obviously a complete webpage with precomposed textures would take more.https://twitter.com/julienPauli/status/1042113172143067138 …
-
-
replace were often much larger, even if you add the size of the browser itself. flash footprint of a modern Android app on the order of 100 MB isn't OK, but this is a problem inherent to the way Android evolved as an open platform and not computing in general.
-
you're complaining about bloat in general, but there's no such thing. some of it only appears to be bloat, and some of it has to be dissected on a case by case basis to get any useful insight. classifying programs by bloat is like classifying cats by number of toes.
End of conversation
New conversation -
-
-
I agree we too often talk about bloat without considering the trade-offs we make, but a payload of 10MB of JS (often compressed, so really more to the parser and compiler) is a UX disaster for median mobile hardware. Apologies if I totally misunderstood you.
-
hang on. 10 MB of minified JS is a lot of code, so it's fair to compare it to a comparably complex offline app. it'll take a bit to download and compile, but apks don't start instantly either, right? am I missing something that makes webapps much worse in this context?
-
Most of that 10MB is usually analytics or poorly optimised usage of multiple JS frameworks.
@nikitonsky's blog post itself was 15.46MB before he optimised it to 730KB once people pointed it out. -
But of course that optimisation was done quietly without an addendum to the blog post or any kind of analysis of how that 15MB blog post happened in the first place because that's harder than writing a shallow rant. Maybe I should write a rant about lazy misleading rants.
-
incredible. i rest my case
-
In the interest of not being completely negative, one good effect of this blog post has been that people are at least talking about this very real problem. The next step is talking about it in a descriptive and analytical way and figuring out processes to fix it.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.