It's right that callback model sucks, and the task model is a way to go.
Sadly, many developers when they hear the word "C# async"
...
All of these statements are made by people that have yet
to study C# async or to grasp what it does.
But it's unpleasant to see the author is talking concept of task - lightweight threading, coroutine, or whatever - is like a patent of C# (or F#). And furthermore, treating many developers are not able to understand this concept.
Maybe true for the people around him.
I understand his position as a lead developer and an evangelist of Mono/C#, but this attitude is ridiculous.
Maybe true for the people around him.
I understand his position as a lead developer and an evangelist of Mono/C#, but this attitude is ridiculous.
But it's unpleasant to see the author is talking concept of task - lightweight threading, coroutine, or whatever - is like a patent of C# (or F#). And furthermore, treating many developers are not able to understand this concept.