3 ms·
OK my understanding is that servo is a browser. Then I read this on their repo: >Servo aims to empower developers with a lightweight, high-performance alterna
by nonethewiser 1y ago
OK my understanding is that servo is a browser.
Then I read this on their repo:
>Servo aims to empower developers with a lightweight, high-performance alternative for embedding web technologies in applications.
Um... what? Are they just saying it's a browser in a verbose way or what? It just seems like you could replace literally all those words with "browser" and the clarity would skyrocket. Although perhaps it's not actually just a browser and I dont understand.
- duped 1y ago> Servo is a prototype web browser engine
- nonethewiser 1y agoYes, those words are also in the repo.
- nicoburns 1y agoTo many people involved in browser development there is a distinction between the "browser" (Chrome and Firefox, but also Opera, Brave, Arc that don't develop their own engine) and the "web engine" (Blink, WebKit, Gecko). Servo is currently more of the latter than the former as it's UI is a pretty minimal one that is mostly useful for testing and doesn't much of the niceties that users expect of a modern browser (bookmarks, history, password manager, etc). I do agree that it's confusing for most people though.
- nonethewiser 1y agoOK, that is a fair distinction I guess. A browser engine would be more clear then, I think. That is what it says in the readme.
- Philpax 1y agoServo is to a browser what Chromium Embedded Framework is to Chromium. It is the vast majority of what is necessary for a browser, but it is not a browser in itself: it renders websites, but all of the user-facing browser functionality around that is a separate concern.