Building a browser using Servo as a web engine

servo.org

140 points·TangerineDream··13 comments

Servo is entering the most difficult age... How the performance hacks will affect security and isolation

The puberty of web engines!

While super excited for servo being made into a browser, I am disappointed in seeing OpenGL at the core of it.

Promising a better battery life while having better performance, better drivers and wide support, I really don't see how Vulkan is still not the first choice when it comes to GPU stuff.

If they put the URL in the title bar, where does the page title go?

On the URL bar. The URL shows when you click on it

This has always felt like an anti-pattern to me. Especially with phishing still being a significant risk for the average person. The remote server controls the page title which means that it's inherently untrustworthy for determining where you are. The URL is controlled by the user/browser/agent which makes it the more trustworthy value. There's value in a page title, but it's not analogous to a URL and shouldn't mask it.

Probably in same place as in Safari.

> "we can draw our UI with additional webviews. The main reason we want to write UI using Servo itself is that we can dogfood our own stack and verify that it […]"

It's XUL again.

XUL was a different stack. This is using the same stack.

You are right, the "HTML-is-the-UI" confused me. Related but different.

A general superpowered UI framework is the primary purpose of a browser, I don't see why it ever needed a second UI framework just for the chrome. Maybe HTML/CSS just wasn't up to snuff at the time.

Godot says the UI is Godot code but doesn't feel like it.

This is a great thing! Custom browser UI is just a custom web page!

Reply on news.ycombinator.com