1067

submitted 6 months ago by Maven@lemmy.zip to c/programmer_humor@programming.dev

100 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] 5C5C5C@programming.dev 43 points 6 months ago

Your graph also cuts out early. Eventually you want to get performance gains with multi-threading and concurrency, and then the line drops all the way into hell.

[-] xmunk@sh.itjust.works 17 points 6 months ago

Good Afternoon Sir, have you heard about our lord and savior pthreads?

[-] 5C5C5C@programming.dev 27 points 6 months ago* (last edited 6 months ago)

I'm not saying you can't do multi-threading or concurrency in C++. The problem is that it's far too easy to get data races or deadlocks by making subtle syntactical mistakes that the compiler doesn't catch. pthreads does nothing to help with that.

If you don't need to share any data across threads then sure, everything is easy, but I've never seen such a simple use case in my entire professional career.

All these people talking about "C++ is easy, just don't use pointers!" must be writing the easiest applications of all time and also producing code that's so inefficient they'd probably get performance gains by switching to Python.

[-] deadcream@sopuli.xyz 7 points 6 months ago

That's the problem of most general-use languages out there, including "safe" ones like Java or Go. They all require manual synchronization for shared mutable state.

[-] 5C5C5C@programming.dev 20 points 6 months ago* (last edited 6 months ago)

There's a difference between "You have to decide when to synchronize your state" and "If you make any very small mistake that appears to be perfectly fine in the absence of extremely rigorous scrutiny then this code block will cause a crash or some other incomprehensible undefined behavior 1/10000 times that it gets run, leaving you with no indication of what went wrong or where the problem is."

[-] uis@lemm.ee 4 points 6 months ago

that's so inefficient they'd probably get performance gains by switching to Python.

Damn, this goes hard for no reason.

[-] uis@lemm.ee 1 points 6 months ago

Well, threadsanitizer catches them in runtime. Not sure about GCC static analyser and other SA tools.

[-] 5C5C5C@programming.dev 3 points 6 months ago* (last edited 6 months ago)

I use thread sanitizer and address sanitizer in my CI, and they have certainly helped in some cases, but they don't catch everything. In fact it's the cases that they miss which are by far the most subtle instances of undefined behavior of all.

They also slow down execution so severely that I can't use them when trying to recreate issues that occur in production.

[-] uis@lemm.ee 1 points 6 months ago

They caught lock inversion, that helped to fix obscure hangs, that I couldn't reproduce on my machine, but were constantly happening on machine with more cores.