The new await keyword in C# can be used to write coroutines libraries like this, but instead of you writing the continuations yourself, you can let the compiler slice up your function. You can then leverage the SynchronizationContext class to control which thread the continuations run on.
Looking at the use of libtask in mongrel2 inspired me to play around with the idea of coroutines in C#. The await keyword makes my latest iteration quite small and nice to use.
https://github.com/AustinWise/LibTaskNet
I suppose that main point in node.js is asynchronous execution, and in c# we already have all these features. I actually can’t see a point of this library in production app.
Not only that, but one of the main selling points of Node.js is using one language (JavaScript) for both client and server programming: the holy grail of Web application development.
A more serious attempt at this was Manos de Mono which has also since been abandoned. With Node getting a lot of love from MS there's little need for a clone.
While we're at it, I'll throw in my demo of node.js style closures triggered by events on I/O with PHP and libevent: https://github.com/hinathan/edges-php
Node.js is becoming a first class citizen on Windows, so I'm not entirely sure what the point of this is. IISNode even allows you to host your Node.js apps in IIS.
.net is incredibly well optimised for web apps, with built-in connection pooling and countless other goodies. For anything non-trivial I'll bet that a normal .net application will blow this out of the water in terms of performance.
It's not async and it is quite heavyweight. Your claim that ".net is incredibly well optimized" is true only for certain definitions.
The output of a really simple ASP.NET MVC hello-world app is measured in a couple of hundred requests per second without even touching the database. If you do the same on top of Node.js or Netty or Twisted, you're speaking about tens or even hundreds of thousands of requests per second.
For anything non-trivial I'll bet that a normal .net
application will blow this out of the water in terms of
performance.
That's not true, not even if you're comparing ASP.NET with normal web frameworks, such as Ruby on Rails.
You can get a lot of performance out of ASP.NET, but to do that you've got to rely on pretty ugly optimizations. To get a taste of what I'm talking about, check out this slightly old, but still relevant presentation: http://blog.whiletrue.com/2009/04/aspnet-mvc-performance/
TL;DR the author went from 5.9 requests / second to 390 requests / second, but to do that they had to cut out many nice features of ASP.NET MVC that used runtime introspection and they also added caching, something which you do anyway in any other web framework available.
Again, for some applications you can go fully async and speak about tens or hundreds of thousands of requests per second served by the same server.
If you read the errata of that post you'll see that the author could have got to 390 requests a second by turning off debug mode. No ugly optimisations necessary.
Looking at the use of libtask in mongrel2 inspired me to play around with the idea of coroutines in C#. The await keyword makes my latest iteration quite small and nice to use. https://github.com/AustinWise/LibTaskNet