693
manyThreadsAreBetterThanOne (sh.itjust.works)
submitted 2 years ago by to c/programmerhumor@lemmy.ml
41 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] -1 points 2 years ago (21 children)

This feels like AI

  • permalink
  • fedilink
  • source
  • hideshow 21 child comments
    •
  • [–] 121 points 2 years ago (13 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 20 points 2 years ago* (4 children)

    Apart from the fact that bubble 1 and 2 point to the wrong person.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 29 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 11 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 9 points 2 years ago (6 children)

    🤦🏽‍♀️ 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 2 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 years ago (2 children)

    lol your operating system is using queues and buffers with multiple threads everywhere.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 18 points 2 years ago (3 children)

    You have exactly 10 seconds to get the duck out of programmerhumor

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 2 years ago (2 children)

    Why is there a duck in your programmerhumor

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •