3 ms·
> At this point, it feels like a matter of time before Rust replaces C/C++. I expect Rust's successor might have a shot at replacing C++. By the time C++ was
by justin66 2y ago
> At this point, it feels like a matter of time before Rust replaces C/C++.
I expect Rust's successor might have a shot at replacing C++.
By the time C++ was as old as Rust, it had conquered the world. If Rust coulda, it woulda.
- caspper69 2y agoI think you're right. As soon as you start writing big(ger) software in Rust, its lacking ergonomics really become apparent. .as_mut().unwrap().unwrap().as_mut().do_stuff() gets really old after a while. And I am not convinced that borrow checking is the panacea that it's made out to be. Region-based memory management can accomplish the same safety goals (provided there's a sane concurrency model), without forcing people into manually opting into boxing and/or reference counting on a per-reference basis. Throw into that the pain of manual lifetime management (it's not always elided, and when it needs to change, it's painful), I honestly believe it's far more reasonable to ask programmers to throw shit into two or three arenas and then go hog-wild with references than it is to expect them to deal with the tediousness of the way Rust does things. We are just cargo-culters (no pun intended).
- jayd16 2y agoI don't think that's fair. There's a lot less blue ocean these days. C++ could expand into virgin territory where Rust (or any new language) needs to fight against momentum.
- deleted 2y ago[deleted]