Mozilla, makers of the Firefox web browser, is the latest tech company to announce layoffs. The non-profit says it is scaling back development on a number
I’d never heard of Servo before this, but judging from the website it’s nowhere near a GUI offering. The work they’re doing on the engine looks solid (to me as not-a-developer) but it’s a telltale sign that there are no UI screenshots on their landing page. So, not an alternative to Firefox yet.
Because, as pointed in the page, Servo is being developed as a(n embeddable) Rendering Engine, not as a full blown end user Browser.
Its alternatives are not Chrome, Safari or Firefox, but Webkit, Blink and Gecko
There’s an example GUI called Servoshell, but it is more of a testing ground and example on how to embed the engine in an app than a serious alternative to anything currently in the market.
Already this kind of work is difficult and daunting. Adding to it a full GUI would make it completely impossible for the current size and financial backing Servo has.
Big words aside it just means that Servo wants to be only one of the parts that compose a real browser: the one that takes HTML, Javascript, WASM and translates them into the things you see on your monitor. All the user facing functionality are left to the devs of the app that embed it.
While it’s not an alternative right now, I think Servo’s focus on being embeddable might help it in the long run. A big issue with Gecko is that it was difficult, if not impossible to embed. It’d be nice to see something like Vivaldi that runs on Servo.
Oh, that’s fair. I’m not complaining about the work being put into a new browser engine, and there is definitely space for improvement over the ones we have.
Vivaldi, though? I’d vastly prefer an open source browser, and maybe one with less baggage than Vivaldi has — but I’ll look forward to any GUI implementation of Servo, when and if, etc.
“trustworthy AI”
Why? Why can’t we have even a single decent browser? Servo is my last hope.
I’d never heard of Servo before this, but judging from the website it’s nowhere near a GUI offering. The work they’re doing on the engine looks solid (to me as not-a-developer) but it’s a telltale sign that there are no UI screenshots on their landing page. So, not an alternative to Firefox yet.
Because, as pointed in the page, Servo is being developed as a(n embeddable) Rendering Engine, not as a full blown end user Browser.
Its alternatives are not Chrome, Safari or Firefox, but Webkit, Blink and Gecko
There’s an example GUI called Servoshell, but it is more of a testing ground and example on how to embed the engine in an app than a serious alternative to anything currently in the market.
Already this kind of work is difficult and daunting. Adding to it a full GUI would make it completely impossible for the current size and financial backing Servo has.
Big words aside it just means that Servo wants to be only one of the parts that compose a real browser: the one that takes HTML, Javascript, WASM and translates them into the things you see on your monitor. All the user facing functionality are left to the devs of the app that embed it.
While it’s not an alternative right now, I think Servo’s focus on being embeddable might help it in the long run. A big issue with Gecko is that it was difficult, if not impossible to embed. It’d be nice to see something like Vivaldi that runs on Servo.
Oh, that’s fair. I’m not complaining about the work being put into a new browser engine, and there is definitely space for improvement over the ones we have.
Vivaldi, though? I’d vastly prefer an open source browser, and maybe one with less baggage than Vivaldi has — but I’ll look forward to any GUI implementation of Servo, when and if, etc.