3 ms·

A browser written in Rust (which is probably Firefox's long term goal) should blow Chrome out of the water in terms of security, despite the massive efforts inv

A browser written in Rust (which is probably Firefox's long term goal) should blow Chrome out of the water in terms of security, despite the massive efforts invested in that regard by Google to prop up Chrome's C++ code base.

chris_wot 8y ago
Would it really though? Sure, there are definitely things about Rust that make coding more secure, but surely that it only one part of security?
- Yoric 8y ago
  Indeed, that's only one part of security. But it's a pretty big one!
- tinus_hn 8y ago
  Definitely, it prevents the buffer overflow style of exploits but there’s also a lot of leaks in how all the DOM objects interact.
SilasX 8y ago
Google doesn’t have military grade static analysis that rejects anything that could allow buffer overflow attacks?
- Rusky 8y ago
  No, they don't, because such a thing cannot exist for C++. Any attempt would basically recreate Rust, or something equivalently incompatible with existing C++ codebases.
Paul-ish 8y ago
It seems unlikely that FF will ever be completely written in Rust. More likely that new bits that get added are Rust, and many of the old bits stay C++. If FF gets rewritten in Rust, it will be a decades long effort.
- pietroglyph 8y ago
  I would just add that Mozilla also targets security critical portions with Rust rewrites. You don't necessarily need 100% Rust to be secure (if you have the right security model).