Comparing Browser speed with JS disabled is like comparing car speed without tyres.
So no source yet, only the HN demo render. I might pay attention when the open source is published and can at least pass Acid3 tests and works on all the site I visit, not only the simplest one.
Compare it to Ladybird's [0], where it is nice and simple. They're building a browser, but they're not ready yet. There's no claims as to the future.
It should already be cool enough that you're building a brand new web engine. There is no need for claims about performance, ad blocking or vertical tabs, when you're nowhere near there.
What did the author ever do to you?
Made incredible claims, did not fulfil them. Ergo, heightened scrutiny.
I can make you a browser engine that loads in 0ms by showing a blank page.
Anyway it uses V8 just like all the other Chrome-alikes, so it should have the same performance there.
Almost but not quite.
Web worked just fine without JS and to some extent still does (this site for example). So a better analogy would be something cars were fine without, but now have it and it improves experience (and sometimes bloats it eg one more thing to break).
Electric windows, seat heaters, GPS, come to mind.
Anyway for the record Karl Benz first produced his Patent-Motorwagen in 1885 whereas the pneumatic tyre wasn't to be invented for another two years and even then in faraway Ireland. So in some some sense cars do predate tyres.