You know, I'll just throw this out there: as someone who's written a lot of code with Node backing it, I've run into maybe one scenario where I've brought clien

You know, I'll just throw this out there: as someone who's written a lot of code with Node backing it, I've run into maybe one scenario where I've brought client and server side logic together. They are two separate models, and will most likely remain as such for the foreseeable future. While I can only speak for myself, I'd advocate using it because the language is indeed nice, and much more flexible overall than some of the alternatives. On top of that, it's got several large companies with a vested interest in its development, which is far more than can be said for some of its competition. Really, the point I'd like to counter here is this: your productivity does not skyrocket, and it's not necessarily the reason to want to use JS server side. For example, the JS syntax works incredibly well for event based programming, and is largely tried and true with its use client side. That's a reason to want JS on the server, and I really wish people would quit throwing around the reusability claim like they do.