So there are a few reasons I’m personally interested in it:
It isn’t being created as the “heart” of a browser - i.e. it is a project to develop the engine and not to develop a browser
Supported by the Linux Foundation rather than any of the tech corps like Facebook or Google
Written in Rust - I’m not claiming that this is good because of the language technology itself but Rust is currently very popular with lots of people wanting to learn it and contribute to projects so hopefully this inspires people to get involved with it.
Not a KHTML/WebKit/Blink (or even a Gecko) fork
Repo is on GitHub - Don’t get me wrong, I’m not a GitHub shill, but generally people monitor and know how to use GitHub better than Google and Mozilla’s systems. I’d honestly be just as happy if using GitLab or any other alternatives as they still confirm to that same user experience (and to be fair WebKit is also on GitHub).
And none of those touch on the technology itself which, honestly, I’m not experienced enough to speak on why it is as good as/better/worse than KHTML/WebKit/Blink or Gecko. Words and phrases like “memory safety”, “parallelizing” and “performance” are thrown around but I’ll leave that to the judgement of those who know better. You might like to have a look at some of the links in https://github.com/servo/servo/wiki/Browser-Engine-Research if you are interested in that front.
Can someone who is more knowledgeable about these things explain why I should be hyped for Servo?
So there are a few reasons I’m personally interested in it:
And none of those touch on the technology itself which, honestly, I’m not experienced enough to speak on why it is as good as/better/worse than KHTML/WebKit/Blink or Gecko. Words and phrases like “memory safety”, “parallelizing” and “performance” are thrown around but I’ll leave that to the judgement of those who know better. You might like to have a look at some of the links in https://github.com/servo/servo/wiki/Browser-Engine-Research if you are interested in that front.