3 ms·
I would answer that you can use Rust to your first question. But I agree with your general sentiment that currently C/C++ is the only choice for certain domain
by RubenSandwich 10y ago
I would answer that you can use Rust to your first question.
But I agree with your general sentiment that currently C/C++ is the only choice for certain domains. But there is nothing theoretically stopping us from creating safer system languages. (See Rust and Swift, much less so Swift. But Apple is working towards that goal with the option to disable reference counting in a future version which will give much more predictable performance.)
My argument is that we need to stop pretending that C/C++ is not worth improving. Every time someone criticizes a gotcha of C/C++ HN gets very defensive. We need to kill our gods if we want better ones and I personally think we need better system programming languages because it is far too easy to write bad C/C++ code.
- jackmott 10y agoI agree there are a number of improvements that could be made if we sacrificed backwards compatibility, it is just so hard to get everyone on board.
- pmelendez 10y ago>"My argument is that we need to stop pretending that C/C++ is not worth improving." I don't think that's the sentiment of their communities though. Not sure about C, but in the case of C++ it has been continuously adding significant features in the latest three iterations (C++11,C++14 and C++17), if that is not signal of improvement I don't know what it is