Node.js Reactions

Node.js Culture as a Service.

[nodejsreactions-blog]

When the case for Node to the CTO consists of “because Netflix uses it”

[nodejsreactions-blog]

Why we can’t update our production Node v0.8 app

[nodejsreactions-blog]

When they let me near the new 32-core hardware

[nodejsreactions-blog]

That memory leak that just won’t go away

[nodejsreactions-blog]

When Node.js does drama

[nodejsreactions-blog]

When you listen to the 'error' event after it's already been emitted

[nodejsreactions-blog]

The Node Drama Trolley Problem

[nodejsreactions-blog]

When the Node.js community drama kicks back in to high gear

[nodejsreactions-blog]

warning: possible EventEmitter memory leak detected. 11 listeners added.

by @denormalize

[nodejsreactions-blog]

a.pipe(b).pipe(c)

by @denormalize

[nodejsreactions-blog]

When a module you depend on with ^ publishes a breaking change as a patch

by @denormalize

[nodejsreactions-blog]

When your console.debug statement causes your test testing stderr to fail

by @denormalize

[nodejsreactions-blog]

Maintaining a popular open source project

[nodejsreactions-blog]

Watching the ChakraCore pull request to Node.js

https://github.com/nodejs/node/pull/4765

[nodejsreactions-blog]

When Microsoft open sourced ChakraCore

[nodejsreactions-blog]

The standard learning pattern during NodeSchool

[nodejsreactions-blog]

Typical Code of Conduct related "discussion"