5 ms·
We lost the servo team, but isn't servo complete enough to simmer in maintenance?
by tomxor 5y ago
We lost the servo team, but isn't servo complete enough to simmer in maintenance?
- kroltan 5y agoNot nearly complete enough if you want a browser. MAYBE, if you want a browsing engine / "webview".
- zamadatix 5y agoThat's exactly what Servo was/is, an embeddable browser engine. It was never aiming to build a usable reference servo browser with the engine. The packaged nightly binaries were just to demo the current state of the embeddable engine which is why they were so barebones.
- kroltan 5y agoYes, you're correct, but the ancestor comments kind of implied it being a hope for browsers at large. Bad phrasing from my part too, sorry.
- tomxor 5y agoAhh, i'm talking about the surviving parts that were adopted by Firefox: https://en.wikipedia.org/wiki/Gecko_(software)#Quantum https://en.wikipedia.org/wiki/Gecko_(software)#Quantum I remember it clearly because Firefox got a big performance boost in it's renderer when quantum was released, often it's faster than Chrome.
- simfoo 5y agoWhat features would a browser need on top of regular webview APIs?
- dralley 5y agoNo, not even close.
- tomxor 5y agoWhy not, It's in Firefox, I'm literally looking at it right now.
- kroltan 5y agoSome parts of Servo are in Firefox, but not the whole thing. Swapping your VW Beetle's wheels for a Ferrari's doesn't make it a Ferrari! Even if it improves handling (or whatever I'm not a car person, it's just an accessible analogy)
- dralley 5y agoNo it isn't. Some parts of Servo were adopted into Firefox, but "Servo" is not in Firefox. If you compile servo and point it at the homepage of google, I doubt it renders right now. It was constantly broken even when it had a full-time staff.