3 ms·
Working on mobile it gets even crazier because everything* is shipped to everyone. "Oh we just need to include this lib for that one tiny thing, who cares." T
by flutas 2y ago
Working on mobile it gets even crazier because everything* is shipped to everyone.
"Oh we just need to include this lib for that one tiny thing, who cares."
Turns into
"we're using 7TB of mobile storage around the world for this one tiny feature"
or
"Our app is responsible for ~472TB of mobile storage being used."
(actual numbers I just calculated btw)
*: Some stuff is optimized out, not everything but essentially anything needed to run any part of the app on a users device is included, even if they just need to do one specific thing and nothing else.
- dylan604 2y agoBy on mobile do you mean working as a native app bloating the app size? The "just for one thing" also seems to be a common complaint about NPM as well. I'm sure any package/library managed ecosystem suffers this problem, but it really seems the Node gets tagged with it much more frequently.
- flutas 2y agoYep, so much crud gets included in app binaries that's just dead code feature flagged off permanently. IMO a lot of companies pinch pinnies on this internally ("focus on performance and app size, the app binary is huge!") while jumping over suitcases of cash ("yes, we absolutely need those 8 analytics libs driven by a json blob, of which we've only used one in the past year due to our contracts expiring 4 years ago").