That’s what they pivoted to after being expelled from Mozilla, but that wasn’t the original goal, was it? It’s the safer(?) one they turned to when the job security evaporated.
(Not sure if that changes anything, just feel obligated to point out the retcon here.)
If there is a difference between how specs define something, and how browsers behave (and website expect them to behave), will you choose technical correctness or websites actually functioning?
Technically this has been the big problem of HTML5 vs XHTML, and "technical correctness" lost to actual usability.
I can't speak for Servo, but my understanding is that they have very different goals than we do.
Servo wants to build an embeddable engine for controlled sets of HTML/CSS/JS content, with a focus on modularity and parallelism.
Ladybird wants to build a usable browser for the open web, warts and all, with a focus on compatibility and correctness.
I'm a big fan of Servo and I hope they become a huge success! Competition and new ideas in browser engines will benefit all of us! :)
> Servo wants to build an embeddable engine
That’s what they pivoted to after being expelled from Mozilla, but that wasn’t the original goal, was it? It’s the safer(?) one they turned to when the job security evaporated.
(Not sure if that changes anything, just feel obligated to point out the retcon here.)
It would be very cool if Servo were picked up as the engine for a new browser.
3 replies →
>that wasn’t the original goal
They always aimed for a better embeddable story than Gecko. That and more parallelism in layout and processing.
> It’s the safer(?) one they turned to when the job security evaporated.
Not safer, more like saner multithreading story. Safe rust isn't so much for security as it is safety in a parallel context.
2 replies →
The talk about correctness gets me thinking.
If there is a difference between how specs define something, and how browsers behave (and website expect them to behave), will you choose technical correctness or websites actually functioning?
Technically this has been the big problem of HTML5 vs XHTML, and "technical correctness" lost to actual usability.
Nowadays the spec mostly is "whatever Chrome does".
Firefox has often been forced to just conform to Chrome behaviour, despite differing specs, or because the spec was rejected/not agreed upon.
3 replies →
Servo is just the engine at this point. Ladybird has the whole thing.
Servoshell is the web browser built around Servo, there is also Qt Servo Webview: https://github.com/KDABLabs/cxx-qt-servo-webview