News for hackers. Stuff that matters.
Re:Is Node.js declining already? by falcolas on Saturday June 13, 2015 @10:17PM (#9713589)
> Its killer feature is that the same code can run on the client and the server.

In the deploys I've worked with, this is never actually done. How many Node.js developers actually ship the exact same code to both locations?

Re:Is Node.js declining already? by k__ on Saturday June 13, 2015 @10:28PM (#9713610)
I haven't seen it either.

I think node running JavaScript and having NPM were much more "killer features"

I mean, 99% of PHP-devs already knew JavaScript and NPM give you something like RubyGems without the need to learn Ruby.

Re:Is Node.js declining already? by bryanlarsen on Saturday June 13, 2015 @10:32PM (#9713622)
We do. We have one app where that ability is a key part of its design. I'm sure there are others.

On a different app I was working on yesterday, I was adding a feature. That feature was much easier to do on the server, so I moved a bunch of code from the client to the server. Less than an hour's work in Node, it would have taken several days in any other framework.

Re:Is Node.js declining already? by cnp on Sunday June 14, 2015 @01:18AM (#9713794)
With React.js this pattern has become much more prominent and simple, with pretty obvious benefits being shown with little effort.
Re:Is Node.js declining already? by morgante on Sunday June 14, 2015 @12:55AM (#9713755)
We do. It's great—we can have a fast first-page load time while bootstrapping additional client-side functionality and all subsequent pageloads are ridiculously fast.

This way, we are making our web server "just another client."

Re:Is Node.js declining already? by k__ on Sunday June 14, 2015 @05:11PM (#9716351)
Any directions with this?
Re:Is Node.js declining already? by morgante on Monday June 15, 2015 @12:35AM (#9717533)
We use the Rendr library, which is built on Backbone: https://github.com/rendrjs/rendr