alt Hacker NewsI think if Rust wants to evolve even more aggressively than C++ evolves, then that is a chasm that needs to be crossed.
In lots of domains, having a language that doesn't change very much, or that only changes very carefully with backcompat being taken super seriously, is more important than the memory safety guarantees Rust offers.
Replies
SkiFire13 • yesterday at 7:10 PM
C++ is still changing quite a lot though, just not in ways that fix the existing issues (often because doing so would break ABI stability).
➕ show 1 reply
Gigachad • yesterday at 10:04 PM
Isn’t this solution solved by just compiling your libraries with your main app code? Computers are fast enough that this shouldn’t be a huge issue.
➕ show 1 reply
In my view, this is a good thing.
As a C++ developer, I regularly deal with people that think creating a compiled object file and throwing away the source code is acceptable, or decide to hide source code for "security" while distributing object files. This makes my life hell.
Rust preventing this makes my life so much better.