Servo: Building a Parallel Browser
Linux.conf.au 2015 -- Auckland, New Zealand1 HN recommenders · 2015–2017
23K views · talk · dated · Uploaded 2015-01-16
Jack Moffitt presents Servo, an experimental browser engine written in Rust and designed to be parallel at every level, using multiple cores, the GPU, fork-join concurrency and SIMD. The talk covers motivations, architecture and plans for the project.
HN commenters cite it as a detailed source on Servo's design and performance, including plans to move Servo code into Gecko.
26:53What the heck is the event loop anyway? | Philip Roberts | JSConf EU
JSConf
36:45Rich Harris - Rethinking reactivity
You Gotta Love Frontend
1:12:27CppCon 2015: Andrei Alexandrescu “std::allocator...”
CppCon
51:18Lexical Scanning in Go - Rob Pike
GoogleFOSSSydney
1:42:09Crockford on JavaScript - Volume 1: The Early Years
YUI Library
37:37RailsConf 2016 - Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson
Confreaks
59:34CppCon 2017: Matt Kulukundis “Designing a Fast, Efficient, Cache-friendly Hash Table, Step by Step”
CppCon
42:30RustConf 2018 - Closing Keynote - Using Rust For Game Development by Catherine West
Rust Programming Language
4 comments from Hacker News
In the video (at 35:39), they show the future plans and the plan is to start using bits of Servo code in Gecko. So, they will replace small parts of C++ code with Rust. [VIDEO] One plan was to first replace easy parts, like image decoders (bmp/ico formats). [LINK] It won't be a one big replacement, more like a gradual take over.
After seeing a youtube demo[[1] of how the aggressive parallelisation that is done in Servo (safely possible by using Rust) speeds up this browser, i'm really excited for Servo! Also, i think this will give us a great base for all kinds of browser embedding what is not based on ancient webkit-gtk. There is another nice presentation on Rust and Servo: [VIDEO] [1]: [LINK]
I suspect you will hear a lot of numbers around the time of the 57 launch, and until then people will keep quiet as they try to make the numbers that get revealed as good as possible. For old numbers, you can get some in some of my old presentations at conferences. I think the LCA 2015 one[1] has the most details in that regard. [1] [VIDEO]
Metajack mention power usage with parallelization briefly here[0], but doesn't provide the data. [0] [VIDEO] (2015)