> No deadlocks, races, etc to worry about because lock graph concurrency is complicated. I’ve spent the last two and a half years mainly programming in single-

> No deadlocks, races, etc to worry about because lock graph concurrency is complicated. I’ve spent the last two and a half years mainly programming in single-threaded NodeJS environments with a focus on heavy same-task concurrency, and I’ve still run into deadlocks and races, despite the lack of OS threads involved. However, your point that context switching is expensive, and is why thread-per-core architectures are so common, still holds.