The Mad Science of Node
summary
Examples include a shared ArrayBuffer pointer that bypasses C↔JS overhead and saves about 30,000 extra JS calls per second for heavy crypto loads and lands in core, a live module reload system that works via global indirection but leaks old constructors and memory, and experiments with mutable native strings and pointer-swapping that yield small speedups but produce unpredictable corruption. Some hacks make it into Node core; others reliably explode.
AI-written summary · about
chapters (9)
- 0:00Mad science in Node.js
- 1:24Optimizing process.nextTick
- 4:39Bypassing strict mode
- 6:06Native modules without compilation
- 7:30Dynamic function generation
- 8:53Live module reloading
- 13:59Mutating strings for performance
- 21:10Dangers of optimizations
- 23:02Why mad science matters
related talks
24mYou Did What? Understanding Node.js Optimizations
11mNode.js Performance Optimizations
25mA JavaScript Parody: A Fun Journey through Hot Topics of Node.js and JS
03mTalking about NodeJS
16mTuning Node
49mA Journey into Node.js Internals
49mA Journey into Node.js Internals
41mDissecting NodeJS - How it works under the hood
