Oh man. On the contrary, I firmly believe the current breed of JS heavy sites has resulted in memory issues running rampant across the web. We just don't yet have the tooling and metrics to make that clear.
-
-
-
We sort of have the data - the "crash" reports you can get from the Reporting API (https://developer.mozilla.org/en-US/docs/Web/API/Reporting_API …) shows (in our data) a _lot_ of crashes on mobile devices on some of our more JS heavy pages (thankfully not pages we're carrying fwd), desktops/laptops are rarely affected
End of conversation
New conversation -
-
-
HTTP Archive - Almanac for 2019 provides a good overview of usage and cost. Clearly headed in the wrong direction.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You are clearly exaggerating the problem. Nothing is ever "complete" of permanently solved, but developers today are generally not noticeably constrained by memory. Sure you can point to low end hardware, but improvement in hardware has been exponential for a long time.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.