There's still zero day exploits found in chromium, wouldn't using using this put you at a huge risk of running into malware in the wild that this browser can't protect against?
Verso – Web browser built on top of the Servo web engine
71–80 of 343 posts
Re: Verso – Web browser built on top of the Servo web engine
#72Earlier quoted context omitted.
How many times are they going to rewrite the site? And how can you see the Lit versus React version, is there another link for it?
There is old.reddit.com, reddit.com and new.reddit.com. new.reddit.com is not the same site as reddit.com!
It is so crazy. I normally use "reddit.com" but a few weeks ago i followed a link to an article on "old.reddit.com" and saw I had notifications. I clicked the item and it was all notifications from days ago. So the read status of notifications on old reddit and current reddit aren't linked?
Re: Verso – Web browser built on top of the Servo web engine
#73So we will, in ~5 years time have two new browser, one in Rust and one in Swift. I hope in the process of doing it we will find new ways of doing things.
Is there a good software engineering resource about the complexity of a web engine? I mean, we all know that is complex but what are the critical areas. Performance is one, compatibility another.
https://robert.ocallahan.org/2024/06/browser-engine.html
P.S.: This specific post was written in response to announcement of Ladybird.
Re: Verso – Web browser built on top of the Servo web engine
#74Have a read about Servo, it is binding with SpiderMonkey as JS engine. Is there some chance, that servo decomposed from SpiderMonkey? If it is not, I don't think anyone can tell difference between firefox and other browser use Servo.
There's a lot more to a browser than the JS engine. And in general, we would want all of the browsers JS engines to be essentially the same. I think starting with an existing engine is the most logical approach
True but at this point of time, Firefox and Servo are using the same CSS engine, same JS engine and same compositor and rendering engine.
Re: Verso – Web browser built on top of the Servo web engine
#75Re: Verso – Web browser built on top of the Servo web engine
#76Earlier quoted context omitted.
There's a lot more to a browser than the JS engine. And in general, we would want all of the browsers JS engines to be essentially the same. I think starting with an existing engine is the most logical approach
True but at this point of time, Firefox and Servo are using the same CSS engine, same JS engine and same compositor and rendering engine.
That still leaves you with at least the layout engine, all the DOM apis, all the networking, multi process model & sandboxing, web extensions support, that are different implementations.
Re: Verso – Web browser built on top of the Servo web engine
#77According to https://servo.org/about/ Servo currently passes ~60% of the web platform tests. Does anyone have experience how far that subset gets you on the open internet?
In my tests, it's pretty unusable atm. Probably half of websites render very wrong and servo crashes nonstop.
Re: Verso – Web browser built on top of the Servo web engine
#78Earlier quoted context omitted.
Hackernews and LWN render reasonably correctly in recent nightlies. Reddit does not.
New Reddit or Old Reddit?
New Reddit rendering “properly” is as useful as a chocolate fire guard. Do you want to view this content on the app? You Can Only View This Content In The App, THE APP is the WAY, JUST FUCKING DOWNLOAD THE APP!!!
At least on mobile.
Re: Verso – Web browser built on top of the Servo web engine
#79I hope that this project will succeed. Incidentally, Verso is also the name of Lean 4’s DSL for typesetting documentation.[1] We are running out of words in the English language. [1] https://github.com/leanprover/verso
> we are running out of words
in a 1000 years we'll be making this observation across the galactic internet.
Re: Verso – Web browser built on top of the Servo web engine
#80There's still zero day exploits found in chromium, wouldn't using using this put you at a huge risk of running into malware in the wild that this browser can't protect against?
I agree, no one should ever bother writing a new browser again, too risky. We should just use chrome forever