Was about to write it's a cautionary tale for "let's procrastinate to write x by going meta and bikeshedding on tools and languages" camp but pavlov beat me to it, interpreting what he wrote as sarcasm.
> 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.
There 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.
That's just not true. Over 10 years ago I switched to Chrome because it was much faster but it's been nearly 5 years since I switched back because Firefox was blowing it away
