Node.js™ Reactions ©

Node.js Culture as a Service.
submit your funnies here:

[Node.js™ Reactions © @NodejsReactions]

Video: Hitler finds out about io.js http://t.co/EDOT2FKQ7H

[Node.js™ Reactions © @NodejsReactions]

When the case for Node to the CTO consists of “because Netflix uses it” https://t.co/zuIO7yhMqx

[Node.js™ Reactions © @NodejsReactions]

Why we can’t update our production Node v0.8 app https://t.co/vcvdXZx0cT

[Node.js™ Reactions © @NodejsReactions]

When they let me near the new 32-core hardware https://t.co/8gaKIDvNqG

[Node.js™ Reactions © @NodejsReactions]

That memory leak that just won’t go away https://t.co/ex1naKEI0R

[Node.js™ Reactions © @NodejsReactions]

The Node Drama Trolley Problem https://t.co/eXrw3NHMSd

[Node.js™ Reactions © @NodejsReactions]

When the Node.js community drama kicks back in to high gear https://t.co/L6GpXXOATn

[Node.js™ Reactions © @NodejsReactions]

warning: possible EventEmitter memory leak detected. 11 listeners added. - by @denormalize https://t.co/ufcc3hVUpm

[Node.js™ Reactions © @NodejsReactions]

a.pipe(b).pipe(c) - by @denormalize https://t.co/ZnQorQsMtu

[Node.js™ Reactions © @NodejsReactions]

When a module you depend on with ^ publishes a breaking change as a patch - by @denormalize https://t.co/MNzxryzOQt

[Node.js™ Reactions © @NodejsReactions]

When your console.debug statement causes your test testing stderr to fail - by @denormalize https://t.co/14rXwooh02

[Node.js™ Reactions © @NodejsReactions]

Maintaining a popular open source project https://t.co/E7xE7ePsp6

[Node.js™ Reactions © @NodejsReactions]

Watching the ChakraCore pull request to Node.js - https://t.co/WHNMM6bHOU https://t.co/72q24flXJ8

[Node.js™ Reactions © @NodejsReactions]

When Microsoft open sourced ChakraCore https://t.co/nTQKSE2Xnc

[Node.js™ Reactions © @NodejsReactions]

The standard learning pattern during NodeSchool https://t.co/UCivsyzyd3

[Node.js™ Reactions © @NodejsReactions]

Typical Code of Conduct related "discussion" https://t.co/dA9YxZCK8E

[Node.js™ Reactions © @NodejsReactions]

Hunting bugs with my custom test framework thing https://t.co/qPGN67BpOV

[Node.js™ Reactions © @NodejsReactions]

npm’s licensing controversy https://t.co/J1CVggjAsG

[Node.js™ Reactions © @NodejsReactions]

Playing with some ES6 https://t.co/tlmihRFaRo

[Node.js™ Reactions © @NodejsReactions]

Arguing about whether we should use v4 or v5 in production https://t.co/CXwYozjo79

[Node.js™ Reactions © @NodejsReactions]

Showing my complex deployment script to ops when it fails due to a random npm error https://t.co/1ndixxCDuu