Lets talk about fibers

[Suliman via Digitalmars-d]

> Simply picking a worker thread + worker fiber when task is 
> assigned and sticking to it until finished should work good 
> enough. It is also important to note though that "fiber" is not 
> the same as "task". Former is execution context primitive, 
> latter is scheduling abstraction. In fact, heavy load systems 
> are likely to have many more tasks than fibers at certain spike 
> points.

Could you explain difference between fibers and tasks. I read a 
lot, but still can't understand the difference.