3 ms·
I agree that they're the wrong architectural primitive almost all cases. If you're doing "new thread()" in the meat of your code's business logic, you've lost.
by monocasa 7y ago
I agree that they're the wrong architectural primitive almost all cases. If you're doing "new thread()" in the meat of your code's business logic, you've lost.
There's a lot of reasons why you want threads though that aren't your CPU hitting 100%. Less janky UI for some systems is one of them.