SpiderNode, V8Monkey, and You
summary
V8Monkey: V8 API for SpiderMonkey wraps SpiderMonkey so Node can run on it; SpiderNode: a Node clone that uses V8Monkey and it works. They ported Node buffers around typed arrays, rewrote buffer internals for API mismatch, and demoed generator-based task.js servers with no transpiler. Benchmarks show mixed GC tradeoffs, some workloads competitive; empty Node chat process sits at ~11–12 MB and current builds still have memory leaks. Build is configure and make.
AI-written summary · about
chapters (16)
- 0:00SpiderNode and V8Monkey intro
- 3:04Why build V8Monkey and SpiderNode
- 6:13Demo with task.js
- 8:45Acknowledgments
- 9:27E4X and experimental features
- 10:30Performance vs V8 in Node.js
- 12:12SpiderNode and Harmony features
- 12:54Debugging and memory profiling
- 13:56Binary data handling
- 15:19API translation challenges
- 16:46Memory leaks in SpiderNode
- 17:48String performance
- 19:12Generator functions
- 19:55Better benchmarks needed
- 20:39Building SpiderNode
- 22:44Q&A








