Weakness in the eye of the beholder.

Agreed. And if the beholder stands a mile away atop a pedastal, they get a particularly bad view.

Your throwaway, uninformed, and fatuous statement is equivalent to saying that "Using Unicode is bad, because it leaves you open to getting all them funny foreign characters".

FYI: Ithreads do not "randomly deadlock or corrupt from race conditions".

Indeed, you may start as many threads as you like and leave them running until doomsday, and they will never do so, unless you, the programmer, create the a situation in which that can occur. And it is just as possible to create either of those errors when programming communications between processes.

So the programmer can create these problems whenever they write bad IPC code. Your conjecture that this is a "threads problem" is just FUD.

However, if you need to communicate between asyncronous tasks, then iThreads provide mechanisms--coded by experts to avoid those problems--that mean that the programmer can avoid having to learn how to perform the communications themselves.

Ergo, if you need to multitask, and you need those tasks to talk to each other, it is easier, safer and quicker to do that with threads. It isn't even complicated--done correctly.