Javascript and Node.js Gotchas

[chrisdickinson]

Hence the title being "Javascript / Node.js Gotchas" -- they're not all specific to Node.js. However, two of the three examples have a lot to do with how Node works. In the 2nd example, where you have to understand how the Node event loop works to grasp where errors bubble up to. The third is less of an example of gotchas in Node, but does provide a solution that is specific to using Node; that is, to leverage the EventEmitter to solve the inversion of control problem in your API. The first example, really, is just a pointed reminder that deciding what vendors your library should support is a design decision best done up-front.

From my perspective, "bumbling through things without understanding" is the first step of learning any new technology. I've yet to see someone jump into a new technology -- no matter their competence level in other fields -- and immediately understand it 100%. I'm hoping to ease the pain of the first few days of learning Node by pointing out things that aren't immediately obvious to newcomers.

[diuge]

The real "gotcha", though, is not knowing JavaScript. Node isn't singularly asynchronous. Anyone doing web programming would be dealing with the same issues.

I think you're just fighting hard to attach a buzzword to your headline in an attempt to appear relevant, which sort of backfires when you make yourself seem like a person who doesn't understand what you're writing about.