Knock knock
Race condition!
Who's there?
Post funny things about programming here! (Or just rant about your favourite programming language.)
Knock knock
Race condition!
Who's there?
good one! i have to admit I didn't get it until I was browsing the comments and then it hit me π
I'm embarrassed to say I only finally got it now. After reading the joke last night. -_-;
vroom vroom, race conditions ποΈ
I'm actually an expert in multiprocessing, which is just as good
Just out of curiosity, can locks be used in multiprocessing?
You have NO IDEA how hard my autism hates you!
I don't get what's supposed to be wrong here, it works on my machine
I am feeling confused with this meme. I am going to escalate this to my manager, secretly hopong he'll tell me to do something else while he passes this on to the one dude in my team who's worked with multithreading that one time.
Iβd like to play ho-pong too.
This is the first time I enjoy a meme of this format / situation.
This feels like AI
Not a lot of programmers on programmerhumor these days are there?
Half of the people posting here act like they are terrified of using threads. Then someone is explaining what a race condition is and they get 100+ upvotes like they just solved world hunger.
You have exactly 10 seconds to get the duck out of programmerhumor
Why is there a duck in your programmerhumor
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]
I don't think it is, the joke is a bit poorly executed, but if you look at the text, the speach bubbles were made white by hand
In case you are serious: It's probably not.
When you're not careful with parallel processing / multithreading, you can run into something called a "race condition", where results of parallel computations end up in the wrong order because some were finished faster than others.
The joke here is that whoever "programmed" this commic is bad at parallel progmming and got the bubbles in the wrong order because of that.
The image makes perfect sense if you read it in the order 3, 1, 2.
The image makes perfect sense if you read it in the order 3, 1, 2.
OH!
I was assuming the joke was that 1 and 3 got swapped around. Because it doesn't really make sense for 2 to be mixed up, considering it's from a different person entirely...
Which meant that the joke just made no sense, because swapping 1 and 3 is just as nonsense as the original order.
π€¦π½ββοΈ Thanks for explaining, my brain must have corrected the race condition.
Regarding threads: I have had good experience with using thread safe queues everywhere to exchange data between threads, it's the right tool in many cases, but I doubt queues to be useful when coding for performance.
Umm, queueing is standard practice particularly when a task is performance intensive and needs limited resources.
Basically any programming language using any kind of asynchronous runtime is using queues in their scheduler, as well.
Could be I was not clear when I wrote performance, I am talking about High Performance Computing, where you want to spend all CPU cycles on solving your problem. While taking Amdal's Law into account. https://en.wikipedia.org/wiki/Amdahl%27s_law
Ah gotcha, fair enough. Definitely depends on the workload. If you have compute you want to dedicate to solely to a single task, have at it.
lol your operating system is using queues and buffers with multiple threads everywhere.
Correct, and your point is?
My point is you donβt need to doubt the usefulness of queues for performance.
Apart from the fact that bubble 1 and 2 point to the wrong person.
I think thatβs part of the joke too. Like the whole comic has been written out of order due to race conditions; rather than just the father represents race conditions.
Itβs one degree of humour too far though, if thatβs the case, doesnβt really land.
It definitely landed for me. The aspect of one thread coming out of a totally different routine for no reason was extra funny.
Yes, if you reorder only the text and not the whole bubble it's also correct. =)
Oooh. Thanks for that, makes more sense now.