Steven Giesel • 1/8/2023

No, No, No - Tasks are not threads and they are not for performance!

This article clarifies a common misunderstanding in C#/.NET development: that Tasks are used for multithreading. It explains that a Task represents an asynchronous operation, which is an abstraction for work that can happen in the background, often without requiring a separate thread. The piece distinguishes between I/O-bound and CPU-bound tasks, using analogies to illustrate concepts, and emphasizes that Tasks are about asynchrony, not parallelism or performance gains from multithreading.

0 comments

#asynchronous programming #c #concurrency