3 ms·
> Plenty of time for people to adapt on how to write proper, safer C++ code than using C idioms. See, this is yet another instance of the strawman argument I p
by simplotek 4y ago
> Plenty of time for people to adapt on how to write proper, safer C++ code than using C idioms.
See, this is yet another instance of the strawman argument I pointed out.
This is not a "enough time" problem. It's a resource allocation problem. Time is irrelevant if no resources are allocated to a task. Rust does not add manpower to rewrite things.
Rust fanatics just perpetuate survivorship biases because the project they did with the express purpose of fixing a specific issue ended up fixing the specific issue, and proceed to somehow go the cargo cult way and praise the framework instead of the rewrite effort. It's disingenuous and a gross misrepresentation of reality, and one which will inevitably come around to bite Rust in the ass. We already see backpedalling with regards to some of these claims once Rust started showing up in SVEs.
- pjmlp 4y agoWith enough liability laws, the resource allocation gets sorted out. Of course there are exploits in safer systems languages, memory corruption issues and arithmetic exploits only represent 70% of root causes. We still need to consider the remaining 30%.
- spoiler 4y agoCan you give concrete examples?
- Jweb_Guru 4y agoThey can't. Rust has been way more secure than C++ in the wild.