I think the best course of action is to build elinks-like console interface on top of the Servo[1]. Just without the WebRender and optional JavaScript engine.
My personal opinion is that, for a servo based browser, it's probably better to just use UWP/C++ on Windows, C/GTK on Linux, and SwiftUI on Mac, and just embed Servo via its C-API layer.
Rust shine when it comes to building a safe and fast web engine. For the OS "glue" code, I would stick to whatever is best for each platform.
I was working on replacing QtWebEngine(chromium) for Qutebrowser with Servo. It is very far from ready, most websites do not render correctly and JavaScript is very hit/miss with regards to updating the rendered view.
Simply put: Servo is not possible to use as a daily driver.
Are there any apps that you know of that use Servo as a rendering engine? I'm curious and would like to look at some examples; I thought Servo was intrinsically tied to Firefox.
It seems like you are ignorant about Servo. "We are still evaluating plans to ship Servo as a standalone product, and are focusing on the mobile and embedded spaces rather than a full desktop browser experience in the next two years." https://github.com/servo/servo/wiki/Roadmap
If you are interested in contributing to Servo. I also recommend the talk "Servo and You: a beginners to contributing to Servo" given by Josh Matthews at FOSDEM a couple of months ago. You can find the video here:
Servo is a rendering engine (think WebKit), not a browser. So maybe you'll get an uzbl based on Servo one day, just like you may get a Servo-based Firefox, or it may remain at the state of a research project, with lessons incorporated back into Gecko.
reply