Link Details

Link 791997 thumbnail
User 225256 avatar

By mswatcher
Published: May 16 2012 / 09:18

Unless you’ve been living under a rock for the past couple of years, you’ll have heard the buzz about Node.js, a platform for building network applications in Javascript. If, like me, you’re a .NET developer working on Windows, you’ll have thought, ‘that’s nice, now back to work’. But I think it’s now time to consider adopting Node as a core part of our toolkit. It allows us to do some things far easier than we can with our existing tools, and it’s now mature enough on Windows that you don’t have to jump through hoops in order to use it. There’s a very nice IIS integration story now with iisnode.
  • 4
  • 1
  • 531
  • 282


Add your comment
User 161039 avatar

mheath replied ago:

0 votes Vote down Vote up Reply

This is a dumb reason for considering Node. "Look I can create a web server that does nothing useful in just a few lines of code..."

Even being a Java guy, I can see that the .Net CLR is much more powerful than V8. It makes me wonder why anyone would even consider going from .Net to Node. It makes no sense.

On the Java platform, we have Vert.x now which is architecturally similar to Node but much faster and more powerful. It would be cool to see something similar get built for .Net.

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (4)

Voters Against This Link (1)

Java Performance Optimization
Written by: Pierre-Hugues Charbonneau
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. Java EE7
  5. HTML5 Mobile
  1. Node.js
  2. Debugging JavaScript
  3. OO JS
  4. JSON
  5. Ajax