4 ms·
A lot of companies started with Java or Go, and will consider Rust without ever touching C++. The stigma alone is enough to turn people off. Hell it's going i
by lallysingh 4y ago
A lot of companies started with Java or Go, and will consider Rust without ever touching C++. The stigma alone is enough to turn people off.
Hell it's going into the kernel in 6.1.
C++ runs a real risk of surviving only in the embedded/realtime space in the next 10 years.
- mrkeen 4y ago10 years? That feels too short. C++ is all the operating systems and the browsers and the games and the JVM.
- SubjectToChange 4y ago> The stigma alone is enough to turn people off. C++ has been hated for decades now. The reason it's used is often because you have to. > C++ runs a real risk of surviving only in the embedded/realtime space in the next 10 years. Ten years from now C++ will still be the language underpinning LLVM, web browsers, geometric modeling, machine learning, etc
- lallysingh 4y agoRust means you don't have to anymore. While the old software codebases will keep using it, the new ones won't.
- bsder 4y ago> C++ runs a real risk of surviving only in the embedded/realtime space in the next 10 years. Embedded/realtime? No way. The people I know in embedded won't touch C++ with your 10 foot pole. Most of my embedded code is wrangling various "stacks" into cooperation with one another, and C++ helps me not one whit with that. At the other side, when I'm just poking sensors, C is more than enough. And, as much I would really like embedded communication stacks to be in Rust, all that would happen would be the vendors slapping "unsafe" on everything so they would basically be writing C anyway.
- sidlls 4y agoMore or less this. “Unsafe” as a value proposition loses its luster when it’s ubiquitous in a code base.