Well, I mentioned safe in the comparative degree. Modern C++ could be actually safe if you restrict yourself to a subset of it, that’s sometimes not really practical. I do think that things are improving and with C++26 it’s becoming way easier to write perfectly (memory-)safe code that’s also (subjectively) elegant.
I don’t think it’s a fair characterization. To my understanding there were specific concerns about contracts. Hopefully these will get resolved, or contracts will be moved to C++29.
The C++ spec is absolutely massive. Nothing says elegant like a million different ways to do something.
Python works pretty well and doesn’t have to much overhead. Sure it doesn’t have the same performance as C/C++ or Rust but most of the time you don’t need millisecond level code.
Well, I mentioned safe in the comparative degree. Modern C++ could be actually safe if you restrict yourself to a subset of it, that’s sometimes not really practical. I do think that things are improving and with C++26 it’s becoming way easier to write perfectly (memory-)safe code that’s also (subjectively) elegant.
C++26, you mean the standard that’s been rejected for being so crap?
I don’t think it’s a fair characterization. To my understanding there were specific concerns about contracts. Hopefully these will get resolved, or contracts will be moved to C++29.
The C++ spec is absolutely massive. Nothing says elegant like a million different ways to do something.
Python works pretty well and doesn’t have to much overhead. Sure it doesn’t have the same performance as C/C++ or Rust but most of the time you don’t need millisecond level code.
I do agree and I think it’s wise to narrow C++ down by a lot, and that is a choice you can make when working on a new project.