>why would you write a program to use threads if you don't need concurrency? ... exactly. There is no good reason. That's what I'm saying the point of the arti

>why would you write a program to use threads if you don't need concurrency? ... exactly. There is no good reason. That's what I'm saying the point of the article is. However, this doesn't mean that people don't do it. He is saying that the tasks that people typically use threads to solve can actually be solved with an event loop and handlers, thus eliminating all of the messy issues with shared state, race conditions, etc. that true concurrency introduces.