this post was submitted on 26 Nov 2025
190 points (100.0% liked)

Programmer Humor

27488 readers
1391 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
top 17 comments
sorted by: hot top controversial new old
[–] tetris11@feddit.uk 4 points 20 minutes ago

That's because they're using Little Endian in the first picture, and Big Endian in the second picture.

No wonder they've got unpatched race conditions if they used the wrong flag at compile time

[–] ns1@feddit.uk 2 points 20 minutes ago

At the risk of explaining what everyone here already gets: I like how the bottom picture could literally be a diagram of a 4-way deadlock where the buses are threads of execution and the roundabout exits are object locks.

Whereas in top picture there are no passengers and I'm fairly sure the buses aren't moving. Which probably says something about the state of the documentation

[–] Warl0k3@lemmy.world 12 points 1 hour ago (1 children)

hang on, that first image is everything on a single thread...

[–] ZILtoid1991@lemmy.world 9 points 1 hour ago (1 children)

Nah, those are double deckers.

[–] Warl0k3@lemmy.world 4 points 41 minutes ago* (last edited 38 minutes ago) (1 children)

Making the word bigger doesn't mean there's more threads per, it just reduces the number of calls to complete some kinds of ops (and something about RAMing busses into each other and... cache locations? idk I'm sleepy)

[–] ZILtoid1991@lemmy.world 1 points 6 minutes ago

The double deckers are an example of a ready-made solution in the original language's standard library, the lower one is getting multithreading working through the C ABI bindings, using some 3rd party solution, all while multithreading a lot of other tasks in the application.

[–] rizzothesmall@sh.itjust.works 22 points 2 hours ago (2 children)

The tasks are all awaiting each other

[–] Warl0k3@lemmy.world 5 points 1 hour ago

"Save us, SuperScheduler! Doctor resource-locking has us trapped!"

[–] Prunebutt@slrpnk.net 0 points 2 hours ago (1 children)
[–] rizzothesmall@sh.itjust.works 10 points 1 hour ago (1 children)

Would you believe me if I said no?

Also, why?

[–] Prunebutt@slrpnk.net 6 points 1 hour ago (1 children)

Because you've got a lot of comments simply describing the images of the posts you comment on. I've seen obvious bot accounts with that behavior.

[–] JeeBaiChow@lemmy.world 12 points 1 hour ago

Serial parralelization...?

[–] panda_abyss@lemmy.ca 4 points 1 hour ago

All I wanted was to call ‘read’ while I listen on a socket!

Where did it all go so wrong!?

[–] Codpiece@feddit.uk 4 points 1 hour ago

You didn’t read the documentation correctly. You’ve switched road side.

[–] Nomad@infosec.pub 6 points 1 hour ago

That's why they stack the buses instead of linking them.

[–] Gladaed@feddit.org 3 points 1 hour ago

Locky, not lock free!