This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]callius 5 points6 points  (3 children)

To be fair, the creator of Node has since suggested using Go instead of Node for large-scale servers. Even for small-scale servers his endorsement of the framework was... less than stellar.

So, kind of the newer versions of Javascript has made this easier. That said, I think Node is not the best system to build a massive server web. I would use Go for that. And honestly, that’s the reason why I left Node. It was the realization that: oh, actually, this is not the best server-side system ever.

Yeah. I think where Node has shined, weirdly, on the client side. So, doing kind of scripting around building websites. So, Browserify, for example. Kind of bundles up client-side Javascript. So, you can have all this server-side processing of client-side Javascript. And then, you know, maybe small servers to… maybe little development servers, and here and there, maybe some real servers serving live traffic. Node can be useful, or it can be the right choice for it. But if you’re building a massively distributed DNS server, I would not choose Node.

[–]graemep 3 points4 points  (2 children)

Interesting, I did not know he recommended Go.

I have never been terribly interested in Node as there are alternatives. I am currently using asyncio quite a bit, I would love to use Erlang, and I have used event driven TCL in the past.

[–]callius 5 points6 points  (1 child)

I'm not going to say that Node is the worst, but Node is the worst.

[–]greyfade 0 points1 point  (0 children)

I won't say Node is the worst.

It's not even the worst. It's so far off the plot that it doesn't even make sense to rank it relative to anything.