5 ms·
> 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
by falcolas 11y ago
> 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?
- k__ 11y agoI 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.
- bryanlarsen 11y agoWe 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.
- morgante 11y agoWe 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."
- cnp 11y agoWith React.js this pattern has become much more prominent and simple, with pretty obvious benefits being shown with little effort.