I see from Matt Baxter-Reynolds that node.js has been released for Microsoft’s IIS. I’ve had an occassional glance at node.js as I liked the thinking behind it, but I’m going to take a more serious look.

Microsoft are a very good software tool development company, but they don’t pick up on things until they’re reasonably sure that they’re going to be around for a while. They’re a few steps behind the open source/Linux world, only picking up things like MVC and jQuery once it appeared that they weren’t going way. So, their backing of node.js is an important sign that it’s not some flash-in-the-pan, but here to stay.

Node.js seems to be very much pitched as a performance gain, but for me, I like the idea of being able to write code in the same language for 2 purposes. If I’ve written a function for the client side, then why not also use it on the server side without rewriting it? Right now, I have to deal with 3 programming languages: Javascript, C# and SQL. I’d much rather have 1 or 2 less, to make my programming more portable.

I’d really like to find some numbers on how much programmers cost compared to CPU cycles over time. If a programmer is scouring for answers to a problem rather than getting an answer on StackOverflow within a few minutes, how much does that cost a business? That’s not to say that sometimes performance isn’t worth spending money on. If you’re running Google or eBay, then using tools for better performance at the cost of programmer time is probably really worth it, but for most people having reliable and fast tools for development is a much bigger thing than the performance of the software.

Share →

One Response to Node.Js for .net

  1. Tad Huffman says:

    So nice Post for developer and i read somewher that Node .js is really easy to run on windows now, and it run under iisnode. Node.js is an event-driven I/O server-side JavaScript environment depending on the open-source V8 Javascript motor.

Leave a Reply

Your email address will not be published. Required fields are marked *