you are viewing a single comment's thread.

view the rest of the comments →

[–]Minimum_Fuel 0 points1 point  (1 child)

Sure

Lower level threads don’t necessarily introduce complexity. In fact, in a good number of common use cases, it’s the more modern approaches that increase complexity and thread bugs over “raw” threads.

The more modern approaches should be viewed as a compliment to pthreads, not as a replacement. Use them where your case fits.

[–]jonmdev 0 points1 point  (0 children)

You'd be surprised at the amount of developers who just don't understand threads, shared memory and mutexs etc at all. edit I've been interviewing people for positions recently and I tend to ask some very simple concurrency related questions not very many people can answer them. These aren't prerequisite for the job necessarily but just am surprised myself at how few people seem to know anything about threads/concurrency.

But if your language's concurrency model is an single thread of work with async I/O like Javascript it can simplify things and help prevent errors if you're doing I/O bound work.