Wait, I'll throw another out there. I agree with the C++ project owner (who's name escapes me) This isn't a C++ issue, it's a "native C" issue. His statements were something like modern C++, if used with recommended practices is considered a memory safe language.

I'm tired of this whole (my straw man) : "Developers are too dumb and lazy, and continue to have high rates of a particular error, they just need to learn this new language that people keep saying will prevent these issues instead of learning to use the current language with best practices" debate where we need to use rust everywhere, and then rust devs think their safe from memory issues and that it's a massive security talking point to write a bad program in rust and call it secure.

Just stop. Get better. Learn from mistakes. Software mistakes will occur, don't be so reliant on mistake free programming??

Reply to this note

Please Login to reply.

Discussion

my disagreement is not about memory safety

moving that to a GC ends that altogether, though it can at times introduce performance issues with excess garbage

my disagreement is readability, and clarity of concepts

objects are a bad way to model systems, the most salient and important feature of an element of a system is its structure and interface, not its arbitrary fake family tree bullshit

objects lead to very ugly long complicated names, and expensive compilation because of the simple fact that objects are an abstract concept and structures and interfaces are concrete, and this comfortable shortcut leads to errors in logic that lie deeper than just the stupid fucking stack pointer

hard to read, hard to understand, hard to compile = easy to fuck up