2 ms·
While there is something to this, and antialiased fonts and CJKV rendering are particularly beneficial, I mostly don't agree about necessarily using more memory
by kragen 5y ago
While there is something to this, and antialiased fonts and CJKV rendering are particularly beneficial, I mostly don't agree about necessarily using more memory (see https://news.ycombinator.com/item?id=30872388 https://news.ycombinator.com/item?id=30872388). We're talking about orders of magnitude more memory than the screen contents.
As for JS, on most pages the only benefit of those megabytes of JavaScript is that I need to use uBlock Origin and/or Reader Mode to read what I'm actually interested in, the page jumps around at random while I'm trying to read it, Twitter tries to extort me into logging in, DoubleClick and reCaptcha can fingerprint my GPU, etc. Also, a megabyte of minified JS might reasonably compile down into a megabyte of bytecode or 4 MiB of native code, not 64 MiB or 128 MiB. JS's execution model is kind of inherently memory-hungry, though.
64 MiB is for one tab.