The C++ side gives you what you need to create your own seat belt: spools of razor wire and clippers to remove the sharp edges (but no gloves). If you cut yourself, it’s your own damn fault. Real developers have discipline.
But people are still insisting they screw all the benches down. They already put an end on this discussion, saying that’s not an option, but people won’t shut-up about it…
It’d be a subtle addition to the joke if the C++ side didn’t have seatbelts.
The C++ side gives you what you need to create your own seat belt: spools of razor wire and clippers to remove the sharp edges (but no gloves). If you cut yourself, it’s your own damn fault. Real developers have discipline.
As a not-a-developer, this sounds like my understanding of C, rather than C++.
In practice, I tend to agree. It’s easier to avoid shooting yourself in the foot with C++, but it’s still just waiting for you to screw up.
I’m mainly getting at Undefined Behavior (UB), which both C and C++ have plenty of. This article from Raymond Chen has some excellent concrete examples: https://devblogs.microsoft.com/oldnewthing/20140627-00/?p=633
They’ve made a point to add seat-belts recently.
But people are still insisting they screw all the benches down. They already put an end on this discussion, saying that’s not an option, but people won’t shut-up about it…