Rusty 🦀 Femboy 🏳️🌈 to Lemmy Shitpost • 4 days agoRustlemmy.blahaj.zoneimagemessage-square19fedilinkarrow-up1231arrow-down122
arrow-up1209arrow-down1imageRustlemmy.blahaj.zoneRusty 🦀 Femboy 🏳️🌈 to Lemmy Shitpost • 4 days agomessage-square19fedilink
minus-squareTrailblazing Braille Taserlinkfedilink14•4 days agoThe 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.
minus-squareL3ft_F13ld!linkfedilinkEnglish2•edit-24 days agoAs a not-a-developer, this sounds like my understanding of C, rather than C++.
minus-squareTrailblazing Braille Taserlinkfedilink2•3 days agoIn 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
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