e10s support question

[andyprough]

What was written back in 2008 on Chrome's wiki page: ....

I'm no expert, but that long block quote looks like a pile of PR marketing spin to me. Which is all well and good, but it seems that this discussion is about real nuts and bolts stuff, and not PR marketing spin.

[Moonchild]

It isn't even relevant to multiprocess either...
Every JS engine has become slower over time, as well. You know why? Because the company being praised there has been pushing for more and more junk to be loading down the engines.

[ownedbywuigi]

It isn't even relevant to multiprocess either...
Every JS engine has become slower over time, as well. You know why? Because the company being praised there has been pushing for more and more junk to be loading down the engines.

This too. The codebase for every major web browser (minus Ladybird if you call that major) is easily over 20 years old. There are a shit ton of optimisations and better code available that nobody is able to discover because there’s literal decades of old crap.

[UCyborg]

And yet, Chromium is the only one that runs QuakeJS smoothly.

Edit: At least that's what I notice going off experience daily driving 17 years old computer.

Edit 2: Mozilla-based also has this pronounced mouse responsiveness lag that Chromium must have paid special attention too. I only noticed this lag on Chromium in the past when testing on Vista where D3D11 paths were non-functional and it went to D3D9.

Granted, some of it is still there regardless, there's no real fullscreen after all, just not as much.

Edit 3: OK, that's new, QuakeJS site didn't change in years, now it doesn't even load in Pale Moon.

[adoxa]

Edit 3: OK, that's new, QuakeJS site didn't change in years, now it doesn't even load in Pale Moon.

It uses import maps, which I was able to work around, and WebTransport (HTTP/3), which I was not.