Why I’m staying with Node

First and foremost, a big hat-tip to T.J. for announcing his ground-breaking news and farewell to Node.js in favor of using Go. When someone fights with something long enough, they will move on, and in his situation, use the “right tool for the job”

That’s cool. And you can’t not respect that. Duder is awesome and smart.

As for me, I’m staying with Node.js. We still have a rough future ahead of us. But I bet on JavaScript a long time ago, and alas, like English — it’s everywhere.

The problems that T.J. points out with Node.js are very similar to the problems we have in English, metaphorically speaking of course. Error handling is natively error prone, callbacks are harder than regular synchronous transactions, errors, errors, errors. We make grammar mistakes all the time in English, but for the most part, we all understand each other, and have known solutions to fix those mistakes.

Just for fun-sake, if JavaScript is English, then Go would be Hawaiian. Simple, small, effective, less error-prone, less well known, and on its own island. And for that matter, I guess that makes Java, German. I’ll stop.

Anyway, metaphors aside, and rather than tit for tat comparing the nooks and crannies of Go vs. Node — there are several other good reasons to continue using Node.js

Web Applications



Right tool for the job

The Moral



People First. VP of Engineering

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store