Hacker News Reader

It's not the point of being cool or not. If Java, Rails, etc works for you, please go ahead.

But we work on several projects by helping a lot of people at the same time. And need a solution that fits our and our client's purpose and context.

Rails did that to some extent, but I believe JavaScript will help us navigate a larger context.

View on HN

To be clear, I have no stake in which tools you use to satisfy your clients' needs. I think it's great that Node and JavaScript work well for you, but you do compare Rails and JS/Node on this 'coolness' axis:

I also think that the [JavaScript] community is going through a "cool" phase, similar to what happened to Rails in the early days...[A]s Rails matured, it lost it's cool factor and the community stabilised.

You need to look under which title that is, and take the context into consideration. That is one of the reasons used to justify why the community is more active that the Rails one.

Reply on news.ycombinator.com