If you cut that compensation in half you could have funded a small team of devs to have finished Oxidation of Firefox and have a really interesting browser, and potentially a really rich GUI stack, JavaScript Engine and who knows what else for Rust itself as a result, on top of it all being production ready and proven because of the nature of Firefox's reach.
There were major noticeable speed differences in Firefox when they implemented key component in Rust. I say this having used Firefox since 2004.
> If you cut that compensation in half you could have funded a small team of devs to have finished Oxidation of Firefox and have a really interesting browser, and potentially a really rich GUI stack, JavaScript Engine and who knows what else for Rust itself as a result, on top of it all being production ready and proven because of the nature of Firefox's reach.
I'm not sure exactly what you have in mind here but this really isn't true for basically any plausible value of "finished Oxidation of Firefox".
As context for scale, during the Quantum Project, Mozilla imported two major pieces of Servo: Stylo and WebRender. Each of these involved sizable teams and took years of effort, and yet these components (1) started from pre-existing work that had been done for Servo and (2) represent only relatively small fractions of Gecko. Replacing most of the browser -- or even a significant fraction of it -- with Rust code would be a far bigger undertaking.
There were major noticeable speed differences in Firefox when they implemented key component in Rust. I say this having used Firefox since 2004.