Live data from Hacker News

Why Node.js?

news.ycombinator.com

1–10 of 15 posts

Why Node.js?

#1
I am a developer with a very strong PHP background. Experience over 5-6 years in PHP and related technologies.

For the past 6 months or so I have been totally working with nodejs and its eco-system. I do agree its blazing fast and has a very good eco-system. But I really don't believe that it is that much strong in web-development. I guess the only stable web framework is Express. But you have to do alot in it to achieve things. After researching I found Sails.js is gaining popularity and has many features out of the box. But after trying it for a month or so, I found that its very much buggy. The thing that works on my local environment does not work in production, however it has the same technology stack with same versions.

npm packages are outdated, dependencies not updated. I wonder why there is so much hype about nodejs and what it is really good at?

What would you say?

Re: Why Node.js?

#2
I have no experience with Sails.js But I worked with Meteor.js framework.

I spent a little time to understand the framework and was able to develop a web application quickly. May be you can try that.

I have planned to post some regular blog posts / videos on my blog (h2labz.blogspot.com) in the future.

Re: Why Node.js?

#4
What you're describing now is how php was in the early years. I started using it with 2.0, just after it upgraded from perl scripts. It's pretty different ~15yr later (I think it's going on 20 now). Give node some time to mature.

There's a lot more to node than express; that's like the jquery of node.js.... every one uses it, and usually not very well.

Re: Why Node.js?

#5
The best "framework" node.js has to offer is Meteor. Nothing beats Meteor for rapid prototyping so far.

Node was the next big thing a few years ago, I was an evangelist by myself. Today, drawbacks and backlashes appear more and more... so if you plan to reorganize yourself or some products to node, you may just skip it.

I'm personally betting on elixir for everything that is related to "server" or "service", and Rust for when you have to be very close to the metal (or providing an optimized native function to elixir).

Using "universal"/"isomorphic" JS to build everything everywhere sounds good on paper and feels exciting at the beginning, but later you have to deal with these mountains of layers of wobbly code, when stuff begins to break badly. Not to mention that JS becomes an ugly beast of a language, crammed with loads of useful features without a thoughtful foundation. But, this is just my experience.

Re: Why Node.js?

#6
It's really good at generating hype...

Like PHP, it lowers the barriers for entry, so you get a lot of new users that aren't aware of any CS prior to 2005 or so. But they like to write blogs and you like to hang out on blog aggregator websites.

Re: Why Node.js?

#7
I still believe a lot of the hype for node comes from the absurdly large number of js-only or virtually js-only developers who enjoy the idea of using the language they have grown so familiar with everywhere where possible.

The trend gets accelerated because most new programmers start with javascript, or soon switch to javascript because they see it as the one language they can do "the most" with.

The fresh blood is, due to being new to programming, very explorative and curious about platforms and such drive the use of (back then) experimental tools up a lot.

I personally think that both PHP as well as javascript suffer from being designed not just with flat-out bad syntax, but also for a rather narrow use case and then being adopted widely for lack of widespread availability of other tools.

As a result they are used in places they were not expected to be used and for systems of scale that they were not intended to handle.

The backend of the future may run with node or it may run with PHP, I hope for neither. There are languages out there with more powerful and safer abstractions, with more carefully designed APIs and standard libraries that do not just clutter the global namespace, with usable import functionality from the get go and with type checking and -inference.

But that's just my two cents, I could be wrong :)

Re: Why Node.js?

#8
post #7

I still believe a lot of the hype for node comes from the absurdly large number of js-only or virtually js-only developers who enjoy the idea of using the language they have grown so familiar with everywhere where possible. The trend gets accelerated because most new programmers start with javascript, or soon switch to javascript because they see it as the one language they can do "the most" with. The fresh blood is,…

> "There are languages out there with more powerful and safer abstractions, with more carefully designed APIs and standard libraries..."

It would be really nice if you could name those languages and your experience with them.

Re: Why Node.js?

#9
post #5

The best "framework" node.js has to offer is Meteor. Nothing beats Meteor for rapid prototyping so far. Node was the next big thing a few years ago, I was an evangelist by myself. Today, drawbacks and backlashes appear more and more... so if you plan to reorganize yourself or some products to node, you may just skip it. I'm personally betting on elixir for everything that is related to "server" or "service", and Rust…

I have not used Meteor yet. Hopefully I will give it a try. But still I see many big companies converting to node.js and praising it in their blogs and everywhere.

Big companies like facebook, paypal, etc are investing in javascript. Using it in places where it was never thought of e.g. "react-native"

Re: Why Node.js?

#10
Oh there are many benefits:

- Need any specific feature? Just give NPM a quick search and you'll find not one, but a dozen half-assed implementations. The wide range of unfinished, poorly tested, not-invented-here packages giving the impression of a pragmatic and vivid community guarantees that the platform won't lose its momentum anytime soon. I mean just look at http://www.modulecounts.com/

- It has a Windows installer so it works on Windows. Guaranteed!

- Significant pool of young, cheap and over-motivated developers that are yet to experience burnout. Not having to deal with employees' family responsibilities or that COBOL dinosaur who just happened to forget his own cubicle number is a big plus.

- Running the same language on the server and the browser means you won't ever have to learn another language. Sans the language that compiles to JavaScript of the month, of course.

Post reply on HN