Chrome Never-Slow Mode Prototype

Re:Chrome Never-Slow Mode Prototype by rifung on Tuesday February 05, 2019 @03:09PM (#19089259)

If the issue of too many DOM elements is memory use, wouldn't it be better to just limit the memory use of a page?

Apologies if this is a really ignorant question as I know very little about browsers/front end development.

[ Parent | on HN ]

Re:Chrome Never-Slow Mode Prototype by developit on Tuesday February 05, 2019 @03:18PM (#19089357)

It's more than memory use - it causes tree traversals to take longer, which means unbounded style recalculations (common) and side-effecting DOM changes take longer.

[ Parent | on HN ]

Re:Chrome Never-Slow Mode Prototype by TomMarius on Tuesday February 05, 2019 @03:11PM (#19089273)

There are legit uses of RAM, fully fledged web apps are ordinary now

[ Parent | on HN ]