549
you are viewing a single comment's thread
view the rest of the comments
[-] danhab99@programming.dev 9 points 11 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.

[-] lime@feddit.nu 7 points 11 months ago

nothing about any of those libraries dictates an OO approach.

[-] Buddahriffic@lemmy.world 2 points 11 months ago
[-] entropicdrift@lemmy.sdf.org 1 points 11 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.

[-] danhab99@programming.dev 0 points 11 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)

[-] lime@feddit.nu 4 points 11 months ago

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

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

Programmer Humor

30162 readers
1426 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