What is angry threads

What is the difference between task and thread?

In computer science terms, a is a future or a promise. (Some people use those two terms synonymously, some use them differently, nobody can agree on a precise definition.) Basically, a "promises" to return you a, but not right now honey, I'm kinda busy, why don't you come back later?

A is a way of fulfilling that promise. But not every needs a brand-new. (In fact, creating a thread is often undesirable, because doing so is much more expensive than re-using an existing thread from the thread pool. More on that in a moment.) If the value you are waiting for comes from the filesystem or a database or the network, then there is no need for a thread to sit around and wait for the data when it can be servicing other requests. Instead, the might register a callback to receive the value (s) when they're ready.

In particular, the does not say why it is that it takes such a long time to return the value. It might be that it takes a long time to compute, or it might that it takes a long time to fetch. Only in the former case would you use a to run a. (In .NET, threads are freaking expensive, so you generally want to avoid them as much as possible and really only use them if you want to run multiple heavy computations on multiple CPUs. For example, in Windows, a thread weighs 12 KiByte ( I think), in Linux, a thread weighs as little as 4 KiByte, in Erlang / BEAM even just 400 bytes. In .NET, it's 1 MiByte!)