By Ev Bogue - October 10th 2013
I've been trying to write this piece for six months. It's a hard piece, and I'm sure it will get me flamed, hated, condemned, and perhaps hunted and killed on the streets of the information superhighway. But this peice has to be written, so I will attempt it. To the sound of Kanye West's Yeezus.
I'm open to hear what you think. I'd prefer if you email me. But you can also find me on IRC at the channels Node.js devs frequent. You can also spread your hate for me all over Hackers News or Reddit, if you so choose. Just know, you hate me because I'm right.
Nutgraf: If you call yourself a Node.js dev, you need to be deploying your website using Node.js. If you cannot figure out how to do this, you probably don't know how to use Node.js in production.
As far as I can tell, the standard workflow for MOST Node.js devs right now is this
What it needs to be is
As far as I can tell, the easiest way to use Node.js code in production is to write a functional website with Node.js. By functional, I mean your code works.
Too many Node.js developers are using non-Node.js software to deploy their websites. This leads me to believe these people, as much as they talk about deploying Node.js, do not know how to use it. If they did, they would use Node.js to deploy their website. Not Tumblr, not Github pages, and you're a fuckwad if you use Medium.
I can count on my right hand the number of Node.js developers I know who are deploying their websites with Node.js. The rest? Using centralized, read EASY, services.
Some of the most well reknown Node.js developers I know have not figured out how to deploy their own website with Node.js. This is a sad state of affairs.
Can you imagine how shitty Linux would be if all Linux developers used Windows or Mac OS X? It'd be pretty terrible, right? Node.js has some pretty rough edges because Node.js developers can't figure out how to deploy their own websites with Node.js.
In parting: eat your own dogfood. You might find it begins to start tasting better.