Re:Google says replacing C/C++ in firmware with Rust is easy
by MBCook on Saturday September 07, 2024 @11:38PM
(#41478025)
The world has lots of important COBOL. You’re dead on. Even if everyone committed to all new code in Rust tomorrow, C/C++ will be around for a LONG time.
There’s just too much pre-existing code.
Re:Google says replacing C/C++ in firmware with Rust is easy
by xelamonster on Saturday September 07, 2024 @10:33PM
(#41477802)
How is "too much existing software uses C/C++" not just inertia? That can also change with time.
Re:Google says replacing C/C++ in firmware with Rust is easy
by doe_eyes on Sunday September 08, 2024 @01:13AM
(#41478334)
Inertia is doing things because you're used to doing them. This is pragmatism: until the arrival of mainstream Rust-based OSes, there's probably no escaping C/C++.
Re:Google says replacing C/C++ in firmware with Rust is easy
by xelamonster on Sunday September 08, 2024 @03:11PM
(#41482405)
My point is that the arrival of Rust-based OSes is absolutely in the cards, so while I don't disagree that it would be very difficult to fully escape at the moment that is also actively changing.
The problem isn't just personal preference or inertia. It's that all mainstream OSes, libraries, and system software are written in C/C++. You can't exactly ignore this and not learn the language if you want to work in this space.
Of course, there are many developers who don't work with system-level stuff, and they may be perfectly fine just knowing Java or JavaScript, but Rust is not positioning itself as a direct competitor to that.