Hacker News Reader

Comment by sakras | Hacker News Reader

The demo fell a little flat because the "before parallel DOM" and "after parallel DOM" boxes were almost exactly in sync for me (Firefox, MacOS).

View on HN

It does say right on the homepage:

> What browsers are currently supported ? Since we depend on the `Origin-Agent-Cluster` header being honored by the browser, we are currently limited to Chrome and Edge.

Maybe it's just me, but I'd argue that they should bring compatibility info closer to the demo section. While I do appreciate the mention in the FAQ at the bottom, that is pretty far away from where the demo occurs.

So, Chrome. Disappointing to announce it as 'upgrade your DOM'.

I used chrome to confirm whether my DOM was upgraded, and saw the same result. The graphs were very synched up.

You might have to wait a few seconds to see the before dropping down in FPS on Chrome/Edge.

It's unintuitive, but I'm pretty sure we're supposed to be looking at the spinning square and not the graphs.

After a while the computations get harder to the point that one of the square's animations starts to become janky, while the other stays smooth.

This example is not intuitive.

The square should be more prominent than the graph, otherwise users will think that they're supposed to be looking at the graphs.

And Edge. This feature has positive signals from Safari/Firefox.

in case you didn't know Edge (like Brave, vivaldi, Opera GX, etc...) these days is just the chromium engine (blink) with a msft chrome.

For 80% of all web traffic, I would still feel its an upgrade.

This is why Chrome is the new Internet Explorer. I dread the day that common websites show a “requires a Chromium browser” pop up.

Except it’s literally the opposite. Chrome gets a lot of hate for being associated with google, but it’s always innovating and implementing the latest standards. Internet explorer, at least in it’s last years was the complete opposite.

Sure, let's take 80% of market share and track users for our own benefits. Standards.

Use Brave. No tracking, latest features. FF needs to get their shit together honestly.

80% of all desktop traffic. Overall maybe 30-45% of all web traffic.

The non parallel was faster for me... But also on FF/MacOS

Unfortunately, the new browser features used in the project are currently supported on Chrome/Edge only. But, FF/Safari have shown positive intent.

I am an FF user myself and super sad to see that :(

Yea I did a comparison between Chrome and Firefox as I did not see any difference on Firefox between the panes.

It does seem to work in Chrome though.

Same here. Pdom stayed at 60fps in chrome, but in firefox it had the same framerate drop off as the sync dom.

On an M2 mac using Chrome. The before dropped down to 60 FPS / 10 MB, while the after was 120 FPS / 5 MB.

you have to wait a while until the before box starts to stutter, maybe 30-60 secs.

Reply on news.ycombinator.com