Servo Architecture: Safety and Performance
linux conf au 2017 - Hobart, Australia3 HN recommenders · recommended in 3 months, 2017-2017
12K views · 9 years ago · talk · dated
Jack Moffitt presents the architecture of Servo, Mozilla's experimental browser engine written in Rust, focusing on parallelism across cores, GPUs and SIMD and the safety properties gained from Rust.
HN recommends it as an exciting look at how a browser can be rebuilt for performance and safety, including the WebRender ideas that fed into Firefox Quantum.
43:29Servo: Building a Parallel Browser
Linux.conf.au 2015 -- Auckland, New Zealand
23K views • 11 years ago
13:44Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 2: Demo
𝓖𝓷𝓸𝓶𝓮💫𝓢𝓪𝓷𝓮
13K views • 10 years ago
15:00Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 1: Rust
𝓖𝓷𝓸𝓶𝓮💫𝓢𝓪𝓷𝓮
19K views • 10 years ago
29:47The Truth about Rust/WebAssembly Performance
Greg Johnston
218K views • 3 years ago
0:14Chrome vs Firefox vs Safari vs Servo WebRender
Jake Archibald
121K views • 10 years ago
52:23Nicholas Zakas: Scalable JavaScript Application Architecture
YUI Library
68K views • 15 years ago
52:54Rust at speed — building a fast concurrent database
Jon Gjengset
225K views • 7 years ago
1:05:59Data Oriented GUI in Rust by Raph Levien - Bay Area Rust Meetup
Rust Programming Language
83K views • 8 years ago
36:16RustConf 2016 - A Modern Editor Built in Rust by Raph Levien
Confreaks
43K views • 10 years ago
35:42Progressive Performance (Chrome Dev Summit 2016)
Chrome for Developers
34K views • 9 years ago
13:45A 10x faster TypeScript
Microsoft Developer
608K views • 1 year ago
22:19Lars Bergstrom - Beyond Safety and Speed: How Rust Fuels Team Productivity
Rust Nation UK
18K views • 2 years ago
51:12Google I/O 2011: Writing Web Apps in Go
Google for Developers
135K views • 15 years ago
48:46Rust's Journey to Async/Await
InfoQ
90K views • 6 years ago
19:36Your web app but good: Aaron Boodman (Local-First Conf)
Local-First Conf
8K views • 2 years ago
44:36Hacker Way: Rethinking Web App Development at Facebook
Meta Developers
900K views • 12 years ago
55:08Rust: A Language for the Next 40 Years - Carol Nichols
ChariotSolutions
367K views • 7 years ago
1:00:29Google I/O 2012 - Meet the Go Team
Google for Developers
108K views • 14 years ago
1:07:46Building a Better Web Browser - James Mickens - Harvard CS Colloquium 2015
Paul Irish
29K views • 10 years ago
56:23Speed Up Your JavaScript
Google TechTalks
136K views • 17 years ago
3 comments from Hacker News
This is a great explanation. I also recommend Metajack's talk on WebRender in Servo: ▶ this video Also go read everything else Lin Clark has done. They're pretty great.
If you have the time there is a nice talk about WebRender: link Here is another great talk: ▶ this video At ~25:30 he'll also talk a bit about Quantum. In a nutshell WebRender is used to send a web page to the GPU which will paint all divs, borders, shadows, images etc. Currently WebRender is the only component I'm aware of that is inside Firefox Nightly. It's still behind a config though.
There seem to be a lot of people that are saying "oh, without XUL based extensions, Firefox is just a (worse) Chrome clone, so I might as well just use Chrome." I think what they might be missing is that Mozilla's conclusion is a lot like the people seem to be thinking here -- even though Chrome doesn't have the fancy extensions that are possible in Firefox, many many more people are using Chrome than Firefox, because they see it as a better Firefox. Clearly, that has something to do with either security or performance, where Firefox has a perceived lag. Mozilla is actively working to improve performance, and you may not want to switch to Chrome after all, because Chrome may instead be the poor man's Firefox (I personally think this is already the case, simply because with my 679 open tabs, Chrome would simply kill itself [44 loaded]). This video is one of the most exciting I have seen with regards to web browser performance, and it's Mozilla: ▶ this video More info on what this means for Firefox: link TL;DR: What if even with the missing XUL extensions, you wouldn't want to switch to Chrome, because Firefox was just plain faster?