2 ms·
> Cautionary tale for the ‘rewrite it in Rust’ camp Mozilla, famously, made multiple attempts to update Firefox's rendering engine to take advantage of multipl
by GeekyBear 3y ago
> Cautionary tale for the ‘rewrite it in Rust’ camp
Mozilla, famously, made multiple attempts to update Firefox's rendering engine to take advantage of multiple CPU cores that had to be abandoned before they switched over to Rust and started to see some success.
>Parallelism is a known hard problem, and the CSS engine is very complex. It’s also sitting between the two other most complex parts of the rendering engine — the DOM and layout. So it would be easy to introduce a bug, and parallelism can result in bugs that are very hard to track down, called data races.
https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-engine-quantum-css-aka-stylo/ https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en...
- o1y32 3y agoRust may have helped but I doubt that's the deciding factor. This needs more context
- GeekyBear 3y agoThere is already a link to an interview with Josh Matthews, who led Servo development, where he makes the case that moving to Rust from C is the factor that finally allowed the effort to succeed after three previous failed attempts. https://news.ycombinator.com/item?id=36093636 https://news.ycombinator.com/item?id=36093636
- kvark 3y agoReminds me of the famous “you have to be this tall to write multithreaded code” poster :)