3 ms·
I still recommend Node.js. Reasons: 1. Node.js is maturing and growing by the day 2. You want to invest in something that becomes better [more reliable, matu
by dshankar 15y ago
I still recommend Node.js.
Reasons:
1. Node.js is maturing and growing by the day
2. You want to invest in something that becomes better [more reliable, mature, documented etc.] over time, and the Node.js community is going to be great over the next few years
3. You don't want to invest in the technology of the previous decade, you want to invest in the technology of the next decade. Node.js is that technology.
4. Building on Node.js lets you have an advantage in hiring because developers that know Node.js tend to be very good hackers [they were curious enough to learn something new].
5. My company, Flotype, is taking Node.js to enterprise with our NowJS offering. Every single major corporation out there, such as Zynga, Google, HP etc. are all working on Node.js right now. Enterprises are looking into the future and are betting on Node.js.
Honestly, there are benefits of sticking with something like Rails, but you should be looking into the future, and the future is Node.js
- rufugee 15y agoCan you point out some substantial applications which have been written with node?
- dshankar 15y agoYes, take a look at Yammer, Voxer, Gilt Groupe's Hummingbird, Etsy etc. The list goes on!
- goldmab 15y ago1. I don't see how this is better than using a system that already has a mature language and libraries. Java, .NET, Python, Ruby, Perl, PHP, et al have that. Yes, Node is catching up very quickly. But how is catching up better than being ahead? 2. This is a restatement of the first reason. 3. How do you know that popular technologies right now are going to decline? Java was popular ten years ago, and it's still popular. Python was not popular ten years ago, and now it is. I don't expect either to decline in the next ten years. Node, on the other hand, could very well stop growing, or even recede. 4. Why would you require Node experience? A good web developer should be able to pick it up quickly. That allows you to work with the same general talent pool as if you were hiring for Rails or whatever. 5. This is a restatement of reasons one and two.