Hacker News new | past | comments | ask | show | jobs | submit login

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.




Have you read the article? It's not about tasks per se, it's about a code rewriter.


This article is about structural paradigm shift which foresaw for a long time from Actor model, Erlang, and recently to Go and Rust.

How is this just only an introduction to a new syntactic sugar?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: