Pitfalls of Node.js

Too Long; Didn't Read

Lately, I’ve been writing lots of Python and Go, but if you know anything about me, you’d know <a href="http://tejas.io/" target="_blank">I</a> <a href="http://www.meetup.com/nashjs/events/224842082/" target="_blank">was</a> <a href="https://medium.com/@tejasmanohar/i-m-on-the-koa-js-team-14a72717504d#.k4vvn14ni" target="_blank">once</a> <a href="https://medium.com/@tejasmanohar/babel-6-and-mocha-657923628b9c?source=user_profile---------4-" target="_blank">a</a> <a href="https://medium.com/@tejasmanohar/understanding-es6-const-ab448906c4e1?source=user_profile---------10-" target="_blank">major</a> <a href="https://nodejs.org/en/" target="_blank">Node.js</a> <a href="https://github.com/tejasmanohar/npm-algos" target="_blank">advocate</a>. Recently, when I’ve had to stretch my fingers to write a quick “life hack” or number crunching script to speed up my day, I haven’t been thinking of JS, so I definitely can’t call it my go-to language anymore. That said, since I once did, I believe I have the right to criticize it… so, let’s get started.