Async/await really is a great abstraction on top of task parallelism; it's easy to understand without having to wade through a zillion blog posts explaining how it's just like burritos, Lego blocks, the OSI model, or homeobox genes, or underpants. Which means that it's something you could actually get away with using in enterprise software development, rather than something that'll earn you a reputation for developing software that your colleagues wouldn't be able to maintain.
I have to disagree to you also on the ground that almost everything in Haskell is (and many important things in Erlang are) async without any annotations. Haskell is lazy and that alone makes many operations "asynchronous", so to say. It's run-time system is heavily threaded and employs work stealing to fit millions of green threads into several system threads.
You can write your own scheduler [1] for your purposes, if you please. As fine grained as you want it to.
[1] http://hackage.haskell.org/package/meta-par
In fact, .Net is years behind of Haskell and Erlang. Just because it borrows features from Haskell (and other languages) libraries and bolts them into language.
The difference here is that things in libraries are first-class, you can create them at run-time. That does not often apply to language constructs.
thirsteh's cynicism is misplaced. node.js is effectively predicated on asynchronous implementations, and you have to work hard to do otherwise. The end result tends to be very efficient implementations that can serve large numbers with ease. .NET bolted on asynchronous sugar as it matured, and while that is very good, and you can make efficient implementations, most don't. So it's not really reasonable to dismiss the talk about one because it's possible in another.
EDIT: thirsteh is continually editing their posts so assume their commentary is very different from what it originally was.
Despite what you seem to imply in your comment, I/O does not block an entire thread in any of these languages, however the control flow in a single thread does block, i.e. err = fireTheRockets() does block until fireTheRockets completes, but performance-wise it is equivalent to fireTheRockets(function(err) { ... }). Only now you're saved the callback spaghetti.
Node.js advocates are literally peddling callback spaghetti as an advantage because "it lets you write much faster applications with ease", yet Haskell's threads and blocking semantics blow any Node.js out of the water by an order of magnitude. (Check out Mighttp/Warp or Go's net/http vs. Node.js.) I come across as cynical because that is sad. It feels like we're travelling back in time, not forward.
The only thing that makes node.js "good" when it comes to threading and async is that it doesn't require synchronization as there is no concurrency. (Same thing for Python with Twisted.) Neverminding that that opens up its own can of worms (I hope you don't do any actual computation in your program, as that's going to block everything): Pretending that it's anything more than that comes across as incredibly ignorant of contemporary language design.
And you would lose.
This conversation was about .NET, and then you (rather oddly) decided to pull in nodejs. It has nothing, at all, to do with Erlang, Go, Haskell, or any other language, and the tactic of using them as the "big brother" to discount another language is petty and disingenuous.
The reason I mentioned those languages is that there is essentially no way (short of using the C ABI) to actually do blocking I/O. It doesn't mean that you can't write performant asynchronous programs in C#.
Maybe you should knock that nodejs chip off your shoulder and get over it. Clearly you had some sort of argument with someone about it at some point, but your arguments just make you look absurd.
Here is what you said: "thirsteh's cynicism is misplaced. node.js is effectively predicated on asynchronous implementations, and you have to work hard to do otherwise. The end result tends to be very efficient implementations that can serve large numbers with ease."
This is what I responded to. Your statements are simply not true. And no, I wasn't the one who brought up node.js either.
My gripe with node.js is that it claims to be something much greater than it is, and people gobble it up. If you want to write Javascript, sure, it's a great tool. Just don't try to sell it as the only, or even a good way to write fast applications. That is what is disingenuous.
Your quote comically excludes the preceding paragraph about .NET, and the following sentences specifically contrasting .NET with nodejs. Instead you continue this transparent charade of pretending that I said something that I didn't.
This boring side discussion is done. You have said absolutely nothing of value, but should feel relieved that you took a irrelevant shot at nodejs for no particular reason.
I do, however I fear it will do very little to stem the tide of frontend developers discovering the awesome powers of asynchronous callbacks in Node.js, and continuing to repeat the meme that it is the best way/a good way to write fast applications. Every other thread on Hacker News is about Node.js these days.