Hacker News new | past | comments | ask | show | jobs | submit login

I've been working on a project that uses node for the better part of the year. I'm in charge of most of its architecture and design.

After all these months, my conclusion is exactly the same as yours: there's nothing that can be done in done that I can't do better in other platform/ecosystem.

Sure, it's unique (event loop) and has a lot of good things (simplicity), but for anything serious, it's lacking real advantages.

Most of my issues with it comes with javascript itself, and the absence of proper tooling. I have no idea of the advantage of choosing this platform given the level of immaturity.

Oh, for those wondering: Node was chosen by a person caught on the hype (my boss, a friend and mentor who can make mistakes as anyone), who hadn't done any real world programming in it (only hello world stuff).




> Most of my issues with it comes with javascript itself, and the absence of proper tooling.

Does anything in ES2017, FlowType, or TypeScript resolve your issues with Javascript itself? If not, what are the three biggest?

> absence of proper tooling

What do you mean by proper tooling? What are you comparing it to? I think you might find that many of the other modern options also lack tooling in terms of debugging, IDE support, etc.


Right; but C# does everything Node.JS does easier and faster (even the event loop, if you like, although it also has first-class support for threading), and has excellent IDEs, debuggers, documentation generators, etc.


Ah yes, C# has awesome tooling. I thought you were comparing to something like Go.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: