"Windows 95 was 30 MB" is such an ignorant, obnoxious, trite take. a triple buffered framebuffer (which you want for smooth scrolling) for my 4K display is 70 MB in *pixels alone*. Obviously a complete webpage with precomposed textures would take more.https://twitter.com/julienPauli/status/1042113172143067138 …
when just scrolling, you do not want to touch the DOM or pixels on the CPU at all unless you need to reflow the webpage. you render precomposed textures into the framebuffer, including any desired animation or such, all done on the GPU. Servo does this well, WebKit not so much
-
-
in theory if you had non-interleaved RAM dice and the OS could compact physical memory and manage NVM cache cleverly, using less RAM would actually reduce power consumption by powering off unused RAM, but I think it's not significant enough to spend time getting it to work
-
Yeah, an ideal laptop/mobile memory architecture would work like that. With a smart OS, you'd get sleep lifetimes comparable to hibernate, but with instant resume.
-
*makes an indefinite gesture* FeRAM
-
I thought FeRAM doesn't have the necessary speed or density? However, I don't know if this is inherent or just the case with PZT-based FeRAM. I don't think anybody has commercialized a hafnium-based FeRAM yet though.
-
hence "indefinite gesture" :P
End of conversation
New conversation -
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.