5 ms·
From the rust Oxidization page (hip name): - "Crossing the C++/Rust boundary can be difficult." - "For components that are relatively standalone, with small a
by throwaway12iii 8y ago
From the rust Oxidization page (hip name):
- "Crossing the C++/Rust boundary can be difficult."
- "For components that are relatively standalone, with small and simple APIs."
- "This minimizes the C++/Rust boundary layer issues."
Not only does Rust not have a good JavaScript integration story, it doesn't have a good C++ integration story.
Most of Firefox is still (8 years later) not written in Rust.
Chrome with C++ has a waaaaay better safety record than Firefox. Guess what? The C++ in Chrome tries to ensure memory safety for JS.
The C++ Chrome tooling does a better job of memory safety as a whole system than Firefox.
- vthriller 8y ago> Most of Firefox is still (8 years later) not written in Rust. <nit>In part because 1.0 release of Rust popped up in 2015, not 2011.</nit>
- krageon 8y agoYou make a lot of points about Rust and mention Firefox in your conclusion, right after saying Firefox is by and large not Rust. I think your logical argument would be better served by using clear language and a single subject. After you have those two things you can think about coming up with examples.
- throwaway12iii 8y agoThanks for your contribution. It's really good. Your sentences are definitely not too long. You definitely understand the difference between a comment and an essay.
- pcwalton 8y agoNone of this is responsive to my points.
- throwaway12iii 8y agoRust is bad at managing DOM memory in Firefox.