News for hackers. Stuff that matters.
Re:.NET and Node.JS – Performance Comparison by virmundi on Friday March 29, 2013 @07:59AM (#5460296)
Node has threads behind the scenes. The average developer can touch them. As a result, you can make 3 async calls with node and you end up only waiting on the slowest. As a result when the slowest returns you've got all the data needed by the controllers/views. Thus your overall system improves.

You could do this with ASP.NET MVC if you're not using the databindings on the front end and your willing to make your service layer a bit more complex. The code behind could call the service layer, which in turn calls three async methods (futures) that would return your data set. Then the service happily chugs along once it's got its data. This just isn't normaly in .NET world.

Re:.NET and Node.JS – Performance Comparison by trust-me on Friday March 29, 2013 @08:52AM (#5460446)
Buddy, get a clue pls. What databindings in MVC?? C# 5 support for async is excellent (almost as good as F#), recently Python's Guido said he's gone copy that syntax to Python. I don't know what you mean by normaly, I use it everyday.
Re:.NET and Node.JS – Performance Comparison by virmundi on Friday March 29, 2013 @06:48PM (#5463433)
I know that you could some async stuff all the way back with 2.0, but I have never been fortunate enough to be on an enterprise project that uses it. As a result of that and watching questions on StackOverflow I didn't think that such development behavior was common.
Re:.NET and Node.JS – Performance Comparison by trust-me on Saturday March 30, 2013 @11:08PM (#5467543)
There was async stuff in 1.0, but the really good stuff came with version 4.0 and 4.5. The Task Parallel Library is a very nice implementation of the Promise/Future pattern, that came from the functional programming world.