Node.js™ Reactions © Profile
Node.js™ Reactions ©

@NodejsReactions

Followers
4K
Following
0
Media
1
Statuses
395

Node.js Culture as a Service. http://t.co/uKQySBOC2t submit your funnies here: http://t.co/FVuwrB1kCZ

Joined May 2013
Don't wanna be here? Send us removal request.
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
11 years
Video: Hitler finds out about io.js http://t.co/EDOT2FKQ7H.
10
100
68
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
8 years
When the case for Node to the CTO consists of “because Netflix uses it”
0
3
5
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
8 years
Why we can’t update our production Node v0.8 app
0
0
2
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
8 years
When they let me near the new 32-core hardware
Tweet card summary image
nodejsreactions-blog.tumblr.com
0
0
2
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
8 years
That memory leak that just won’t go away
0
0
0
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
8 years
The Node Drama Trolley Problem
Tweet card summary image
nodejsreactions-blog.tumblr.com
0
2
8
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
8 years
When the Node.js community drama kicks back in to high gear
0
2
1
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
warning: possible EventEmitter memory leak detected. 11 listeners added. - by @denormalize
0
6
8
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
a.pipe(b).pipe(c) - by @denormalize
0
1
3
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
When a module you depend on with ^ publishes a breaking change as a patch - by @denormalize
0
3
4
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
When your console.debug statement causes your test testing stderr to fail - by @denormalize
0
2
3
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Maintaining a popular open source project
0
2
4
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Watching the ChakraCore pull request to Node.js -
Tweet card summary image
github.com
(Note from the CTC (Fishrock123): This thread is expected to garner a lot of attention. Comments that are not productive to discussing the technical aspects may be removed.) Enable Node.js to opti...
0
1
2
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
When Microsoft open sourced ChakraCore
0
1
1
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
The standard learning pattern during NodeSchool
0
1
1
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Typical Code of Conduct related "discussion"
0
1
1
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Hunting bugs with my custom test framework thing
nodejsreactions-blog.tumblr.com
0
0
0
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
npm’s licensing controversy
nodejsreactions-blog.tumblr.com
0
2
1
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Playing with some ES6
Tweet card summary image
nodejsreactions-blog.tumblr.com
0
2
1
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Arguing about whether we should use v4 or v5 in production
nodejsreactions-blog.tumblr.com
0
0
3
@NodejsReactions
Node.js™ Reactions ©
@NodejsReactions
10 years
Showing my complex deployment script to ops when it fails due to a random npm error
nodejsreactions-blog.tumblr.com
0
3
3