The JS community is in pretty deep denial today. CPUs won't get faster soon enough to keep the current levels of JS emissions from totally suffocating the mobile web, at which point we'll be the next generation of Cobol programmers -- essential, but not the future. https://twitter.com/malchata/status/1179811899959066625 …
-
This Tweet is unavailable.Show this thread
-
Replying to @slightlylate
Do we have prior art of of similar application runtimes who have managed to reduce the app size footprint?
1 reply 1 retweet 2 likes -
Replying to @auchenberg
Flash set strict size budgets for each release, and that kept things in check for their binary. Chrome has a perennial project to keep our binary & memory growing slowly.
1 reply 0 retweets 1 like
Replying to @slightlylate @auchenberg
The common thread is management support and the ability to stop releases when things regress. Bloat == unshippable.
1:43 AM - 4 Oct 2019
0 replies
0 retweets
0 likes
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.