Also if it was written in anything else, it probably wouldn't get the coverage it gets ;)
(Here's to hoping Rust for Linux continues to drive progress for bare metal Rust!)
You may as well ask "why does it matter if this bridge is made of iron".
Each material has its own qualities, which means its own pros and cons in a given context.
This naive belief that there will be one language to rule them all (and is name is <fill-in-the-blank> ignores history and the world outside of programming in a rather silly way.
I'd be fine with someone building a new browser out of stone, concrete, wood, or even rope.
Just don't build it out of C/C++ because those languages aren't memory safe.
There are risk-reduction strategies one can follow with C++, which offer some fraction of the reduction that Rust does (opinions vary on the value of the fraction). Rust enforces risk-reduction strategies, which in some contexts may be of value all by itself.
Language choice does not eliminate risks in software.
They don't really. It's been shown by many studies that 2/3 of security bugs are memory safety errors. That's the minimum that Rust can eliminate.
It actually should eliminate more because it also has the strong type system and tree-ownership style that help reduce the chance of logic bugs unrelated to memory safety too (similar to Haskell and other very strongly typed languages).
This is probably the biggest data set:
https://security.googleblog.com/2024/09/eliminating-memory-s...
Unfortunately they don't break out non-memory safety vulnerabilities, but they've almost eliminated memory safety vulnerabilities by writing new code in Rust.
Of course there are impressive projects made with C. But we generally don't build large bridges out of wood anymore do we.
Notable, sure. But it could turn out to be Tacoma Narrows bridge.
We never did build large bridges out of wood, I think. For the right context, wood is still a preferred material for some bridges.
Yes we did. They just haven't survived. For example London Bridge was "various wooden bridges, AD 50 – 1176".
2) It mattered enough for you to complain about it for some reason, so look at that reason, then look at its reflection.
- Might be interesting to integretors (FFI, dylib, Rust projects)
- Signals some characters: that it's probably safer than alternatives written in non memory safe languages in same class, has good performance
- Might attract contributors (ie I'm sure there's an intersection of people passionate abou the web and Rust)
- This is hacker news, so it might earn a few extra +1s :P
Edit: formatting