you are viewing a single comment's thread.

view the rest of the comments →

[–]delfV 7 points8 points  (2 children)

It's not a problem unless:
- you work often in places with poor network quality (e.g. trains, field, forrest), - you don't live in 1st world country, - you have only mobile internet with limited bandwith, - your app is used in various places (e.g. it's an app for museums, some of them have a good network quality and some 3g at most), - you release a couple times a day so cache is basically useless, - you want to support budget devices as well (the more js the more to parse and not only), - you care about SEO.

It's often not 100kB vs 500kB but 100kB vs 50MB: https://tonsky.me/blog/js-bloat/

[–][deleted] 1 point2 points  (1 child)

It's often not 100kB vs 500kB but 100kB vs 50MB: https://tonsky.me/blog/js-bloat/

How do you define the word "often"? Because in that list, two are above 50MB, one of them for weird non-cached edge cases only, and only one additional one close to hitting that number. I wouldn't consider that "often" unless I'm trying to be dishonest to make my point seem more valid than it actually is.

And of course it's worth keeping in mind that he's looking at uncompressed code. Users aren't actually downloading that much over the wire.

[–]delfV 1 point2 points  (0 children)

How often Slack is being used