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 6 days ago (2 children)

nothing about any of those libraries dictates an OO approach.

[–] Buddahriffic@lemmy.world 2 points 6 days ago (1 children)

Unless it's java.

[–] entropicdrift@lemmy.sdf.org 1 points 5 days 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 6 days ago (1 children)

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 5 days ago

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