(Servo team member here)<p>So. There&#x27;s a programming language called Rust[1] which Mozilla pushed for and developed (it&#x27;s now developed by a larger community, though Mozilla is still involved). Among other things, it guarantees freedom from memory safety issues and data races. Both are important here.<p>Freedom from memory safety issues gets rid of a whole class of security bugs (common in browsers) in one fell swoop. Lack of data races lets one write concurrent code without worrying; without needing to program defensively everywhere. &quot;Fearless Concurrency&quot; is what we call this colloquially, after a blog post with the same name[2].<p>Fearless Concurrency lets us try ambitious things like making layout parallel. Layout in browsers is the step that takes all the nodes on the page with their hierarchy (the DOM) and computed CSS style, and figures out what goes where. All browsers currently do this in a single threaded way.<p>Servo[3] is a research project by Mozilla. It&#x27;s a browser engine[4] which does layout (amongst other things) in parallel. It&#x27;s written in Rust to make this possible (and to avoid security bugs due to memory safety issues). Webrender is a (succesful!) sub-experiment to see if we can be more like game engines and do as much on the GPU as possible.<p>Here are a bunch of (non mutually exclusive) ways it can go from here:<p>- Bits and pieces of Servo&#x27;s code get uplifted into Firefox&#x2F;Gecko (Gecko is the browser engine behind Firefox). This is already happening[5] (integrating webrender into Firefox is something being discussed, too). This means that Firefox can get some wins without having to wait for Servo to be completed.<p>- Servo gets its own UI and is shipped as a new browser. A promising UI being worked on is browser.html[6].<p>- Servo becomes an embedding thingy to be used like a webview.<p>- Servo replaces Gecko for Firefox for Android: Whilst replacing Gecko in Firefox Desktop is rather hard (the two are tightly intertwined), this is less of a problem in the Android app. It&#x27;s possible that Servo would have its own app that&#x27;s either released under a new name or branded as the new Firefox for Android.<p>- Servo replaces Gecko within Firefox: Hard (not impossible). Probably won&#x27;t happen.<p>[1]: <a href="http:&#x2F;&#x2F;rust-lang.org" rel="nofollow">http:&#x2F;&#x2F;rust-lang.org</a><p>[2]: <a href="http:&#x2F;&#x2F;blog.rust-lang.org&#x2F;2015&#x2F;04&#x2F;10&#x2F;Fearless-Concurrency.html" rel="nofollow">http:&#x2F;&#x2F;blog.rust-lang.org&#x2F;2015&#x2F;04&#x2F;10&#x2F;Fearless-Concurrency.ht...</a><p>[3]: <a href="http:&#x2F;&#x2F;servo.org" rel="nofollow">http:&#x2F;&#x2F;servo.org</a><p>[4]: This is not the same thing as a browser. A browser engine handles the displaying and interaction of a given webpage, but doesn&#x27;t bother itself with concerns like a URL bar, bookmarks, history, a proper UI, etc.<p>[5]: <a href="https:&#x2F;&#x2F;wiki.mozilla.org&#x2F;Oxidation" rel="nofollow">https:&#x2F;&#x2F;wiki.mozilla.org&#x2F;Oxidation</a><p>[6]: <a href="https:&#x2F;&#x2F;github.com&#x2F;browserhtml&#x2F;browser.html" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;browserhtml&#x2F;browser.html</a>