Live data from Hacker News

Verso – Web browser built on top of the Servo web engine

github.com

181–190 of 343 posts

Re: Verso – Web browser built on top of the Servo web engine

#181

Earlier quoted context omitted.

[flagged]

This is wrong. Servo development has picked up steam after merged into Linux Foundation, and multiple increasingly used Rust projects are all betting on Servo for the long term: Dioxus, Tauri, some others I forgot.

[flagged]

Re: Verso – Web browser built on top of the Servo web engine

#182

I'm happy to see work being done in integrating Servo into custom browser chrome. My dream browser would be a servo based Qutebrowser. I can only hope.

I have the same dream, QTWebengine is super cool (chrome based as of version 4 afair) but seems to limit Qutebrowser a fair bit.

Re: Verso – Web browser built on top of the Servo web engine

#184

Earlier quoted context omitted.

I'm sure, but it's also "yet another package manager" because everyone has their own favourite package manager. It's a nit, but it's nice when a README.md goes "you need X, Y, and Z" and doesn't pretend you need a specific method for that. Tiny phrasing change, zero real world difference of course, but it's a nice little sign that the folks running a project know that you know what you're doing on the OS you're worki…

Scoop is the main package manager I've been using for years on windows apart from chocolatey. Dunno many others aside from the official windows one: winget.

I've been using Windows as dev platform since it was called "DOS but don't look too closely", I know chocolatey, ninite, winget, and powershell's own built-in nonsense, and yet had never head of scoop until just now. So... that really just tells us that any application manager we think is popular, ubiquitous, and the obvious choice is still really just a niche program =(

Contrast that to brew on MacOS: ever non-devs know about brew.

Re: Verso – Web browser built on top of the Servo web engine

#185

Does this do anything to improve the browser as a user agent? That is an agent that obeys the user over the server. None of the current browsers are user friendly and none are scriptable except by experts wielding large external programs. It should be possible to write a simple shell script to navigate the web, to log in to web sites, to extract information. Or something like Visual Basic.

Puppeteer, which recently added official Firefox support, allows you to write a simple script to navigate the web and such. [1] btw using the phrase "user agent" in the context of browsers is mildly confusing as it is a specific jargon term. [1] https://hacks.mozilla.org/2024/08/puppeteer-support-for-fire...

that's really an interesting case, most puppeteer and playwright deployments are using chrome. If Verso will be faster they might have an advantage in crawl/scrap/QA.

Re: Verso – Web browser built on top of the Servo web engine

#186
post #133

Earlier quoted context omitted.

I’m slightly more ambivalent than you about it. Swift is a nice language and has better ergonomics than C++ and I imagine a Swift codebase might find more contributors than a C++ one (maybe I’m wrong about that!) I also think it’s separate from the dream of “multiplatform Swift”. For that you need a healthy package ecosystem that all works cross platform, Swift doesn’t have that. But a lot of Ladybird is written at a…

I wonder what convinced Andreas Kling to abandon his own language Jakt [1] in favour of Swift. In the long run, it would be good to have high-level languages other than Java that have garbage collection (at least optionally) and classes, and that are still capable of doing cross-platform system development. I don't know if Swift fits that bill, besides cross-platform ecosystem (a la Java), submitting the language for…

One of the major differences between ladybird as part of serenity and ladybird the separate project is using 3rd party libraries. When what you are building are is for fun and you build everything yourself it makes sense to also build a language.

Ladybird as a separate project has the goal though of something usable in the shorter term. So similarly with switching to 3rd libraries for things I don't think it makes sense to spend potentially years first building the language before building the browser.

Re: Verso – Web browser built on top of the Servo web engine

#187

Earlier quoted context omitted.

> wonder if there’s room for a browser engine that ditches performance and just focuses on correctness and safety Isn't this just the noscript, which breaks most sites to a degree where they're impossible to use or load?

Haha, well that’s what I use now. I think it is the opposite though. I’d like a JavaScript implementation that doesn’t break any sites, but which makes absolutely no security compromises, even if that means they have to give up a lot of performance. Sometimes, I just have to load a site that has JavaScript running. Or is unfortunate, but some work sites don’t work without it, etc. I’m fine with those sites being slow…

Disabling (all of) the JITs is a decent approximation of this. It's very site-dependent as to how much of a performance impact it makes, but for many sites it'll be fine.

Obviously this isn't the same as making "absolutely no security compromises", but in practice most JS-related security exploits go through the JIT iiuc. Your JS will be executed with a safe interpreter, where by "safe" I mean the dispatching and basic value manipulation are going to be simple enough to be bulletproof, and also slow enough to prevent most timing attacks. The underlying implementation of all of the built-in methods is still going to be more vulnerable, but those tend to be relatively safe as compared to JIT-optimized versions of them. They also don't change much, so have been tested for much longer as compared to the JITs that tend to get refactored and rewritten relatively frequently.

Re: Verso – Web browser built on top of the Servo web engine

#188
post #2

According 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?

Hackernews and LWN render reasonably correctly in recent nightlies. Reddit does not.

I have a branch here https://github.com/servo/servo/pull/32619 that makes this significantly better (by greatly improving flexbox support and adding CSS grid support).

Re: Verso – Web browser built on top of the Servo web engine

#189
post #2

According 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?

I just compiled it following the Linux instructions. I honestly thought Servo was better than this. Maybe there's something up with the Linux builds? I'd much rather use Ladybird in all its pre-beta glory than this.

There are two window title bars, one by the OS and one from the application. The text in the URL bar is misaligned and is shifted down by half its height. There's a black bar between the browser chrome and the web view. Entering a domain name without http or https and hitting enter crashes the entire application.

Clicking refresh spawns a new window that sort-of-but-not-really shares the same website being rendered.

Very few websites work. Anything with a cookie banner just plain breaks. I can't tell how to edit the URL bar after failing to load/loading a page. Google.com is very wonky. The search box on Google doesn't seem to take space bar for some reason.

For the websites that do work, rendering is very fast and scrolling is pretty smooth. I can see the potential, but there's a lot of work to be done.

Re: Verso – Web browser built on top of the Servo web engine

#190
post #135

Earlier quoted context omitted.

Which isn't that surprising given it has been underway for much longer, and as built with people with actual browser engine experience. Ladybird isn't that bad in comparison.

FWIW Ladybird is also built by people with actual browser engine experience

Ladybird was mostly developed by one person (Andreas Kilng) with no financing whatsoever ,Servo was mostly developed by a team who was being paid with Mozilla money.
Post reply on HN