Fastest browser engine by far at 500 FPS! Servo Webrender - CSS on the GPU part 1: Rust
๐๐ท๐ธ๐ถ๐ฎ๐ซ๐ข๐ช๐ท๐ฎ1 HN recommenders ยท 2017โ2017
19K views ยท talk ยท dated ยท Uploaded 2016-02-23
An excerpt from a Bay Area Rust meetup on Servo's WebRender, which renders CSS display lists on the GPU at very high frame rates. It explains the approach and demos rendering at around 500 FPS.
HN commenters point to it when discussing how WebRender works and as evidence of what GPU-based browser rendering can achieve.
26:53What the heck is the event loop anyway? | Philip Roberts | JSConf EU
JSConf
24:26The Beauty of Bรฉzier Curves
Freya Holmรฉr
36:45Rich Harris - Rethinking reactivity
You Gotta Love Frontend
1:13:50The Continuity of Splines
Freya Holmรฉr
1:12:27CppCon 2015: Andrei Alexandrescu โstd::allocator...โ
CppCon
51:18Lexical Scanning in Go - Rob Pike
GoogleFOSSSydney
3:36elevated by Rgba & TBC | 4k intro (FullHD 1080p demoscene demo)
Demoscene High-Quality Videos (Annikras)
24:46Painting a Character with Maths
Inigo Quilez
5 comments from Hacker News
>"If performance is not competitive" I don't think this will be a problem. One example... [VIDEO] [LINK]
If you have the time there is a nice talk about WebRender: [VIDEO] Here is another great talk: [LINK] 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.
You should take these advices with a grain of salt because it refers to the legacy rendering pipeline used by current web browers. There is not absolute rule stating that layout and painting must be slow while compositing is not. In fact Mozillians are currently working on a new rendering pipeline[1] based on state of the art rendering tools[2]. This new pipeline should be deployed in firefox in 2018 as a part of the ongoing Quantum project. [1] [LINK] [2] [VIDEO]
I'm sure the future blog posts will have more details, but it has to do with immediate mode vs retained mode APIs. [VIDEO]
According to this: [VIDEO] Firefox's servo engine can compose CSS elements/Display List together at 500 frames / second. Maybe next version of Windows / Linux desktop should use FF's servo engine?