547
submitted 2 months ago by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 9 points 2 months ago

I've always hated object oriented multi threading. Goroutines (green threads) are just the best way 90% of the time. If I need to control where threads go I'll write it in rust.

[-] [email protected] 7 points 2 months ago

nothing about any of those libraries dictates an OO approach.

[-] [email protected] 2 points 2 months ago
[-] [email protected] 1 points 2 months ago

Meh, even Java has decent FP paradigm support these days. Just because you can do everything in an OO way in Java doesn't mean you need to.

[-] [email protected] 0 points 2 months ago

If I have to put a thread object in a variable and call a method on it to start it then it's OO multi threading. I don't want to know when the thread spawns, I don't want to know what code it's running, and I don't want to know when it's done. I just want shit to happen at the same time (90% of the time)

[-] [email protected] 4 points 2 months ago

the thread library is aping the posix thread interface with python semantics.

this post was submitted on 26 Mar 2025
547 points (97.1% liked)

Programmer Humor

24391 readers
892 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