With the exception of companies like Google, large enterprise corporations tend to be very conservative about new technology. So why doesn’t enterprise seem to be afraid of Node, a technology that’s only been around since 2009, and has only started to come into the spotlight in the last few years?
(Editor’s note: Since this blog was posted in 2014, we’ve completed dozens of successful projects in Node. You can check some of them out at our Work page.)
To make an analogy, let’s say your CEO got kidnapped on vacation in France (yes, this is going to be an overly dramatic example), and you need a hostage negotiator, so you start (quickly) shopping around. The first hostage negotiator you talk to specializes in business kidnappings. He doesn’t speak French, but he is passionate about the language. “I’m so excited about French,” he says: “it’s such a fascinating, rich language. I just got done with my first Rosetta Stone module!” The second one you talk to has been speaking French for over a decade, but has mostly experience negotiating the release of children, not adults. Who do you go with? The one who speaks fluent French, of course.
Unlike hostage negotiation, most of our jobs aren’t life-or-death scenarios, but insofar as our careers are our lives, we’re deeply invested in hiring the people who can get the job done.
Of course there are details I’m glossing over. There’s a lot more to know about server-side programming than the choice of language. Understanding web architecture, networking issues, scaling, and databases are important areas as well. That said, the choice of language is what glues all of these things together, and having a common language is much more than half the battle.
Pop Art Director of Engineering Ethan Brown has published two O’Reilly books on the subject of Node.JS:
Originally posted January 6th, 2014.