On Thursday, 18 June 2015 at 22:24:09 UTC, Nick Sabalausky wrote:
On 06/18/2015 05:21 PM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= <ola.fosheim.grostad+dl...@gmail.com>" wrote: The layout/render stuff has to support so much dynamic-DOM cruft on every...single...element...of the page, it's pretty much inevitable that the browser itself is where the bottleneck is on a normal page, rather than network.
My impression is that browsers focus too much on typical layout, which makes using it as a generic programming platform challenging when you scale up. Like, using lots of absolute positioning ought to be easy on reflow, but in my experience it isn't.
But I think it is unforgivable that Chrome still stutters when doing longer animations. The biggest browsers never need to fix their issues because everybody works around them anyway.
(Which is really weird if you look at it from the perspective of someone who remembers dial-up.)
I believe I browsed BBSes with a borrowed 300 baud modem with "earmuffs" that you attach physically to a real phone handset. With a font using 4bit wide characters to get 80 columns on a 40 columns computer. Barely readable. :)
