Is the idea that all languages should be memory safe, if possible, uncontroversial enough at this point that it could be described as "PL consensus"? I would think so, but not sure.
Conversation
Replying to
I would have thought so, but Zig is a thing, and Carbon made its big announcement with zero memory safety, so… I think folks will make excuses for why memory safety is too hard/slow without even trying. Still.
2
10
Seems unfair to accuse the Carbon team of neglecting memory safety when their primary goal is bidirectional interop with C++. If that project is successful, it could be great for the industry, even without memory safety. The alternative would be to RIIR.
1
2
Perpetuating using memory unsafe languages is the opposite of great for the industry. Carbon succeeding would be terrible.
Then what is the best path forward for codebases like Photoshop?
1
Choose a memory-safe language for new code. Build a bridging layer between C++ and that language, then migrate over time
2
6
Show replies