A Tale of Two Asyncs: Open Source Language Design in Rust and Node.js
summary
Compares concrete design decisions: Node.js chooses callback/Promise/async await ergonomics built atop libuv event loop while Rust composes Tokio and futures on top of mio and requires explicitly starting the runtime. Documents governance and engineering evidence: long RFC threads with hundreds of comments, an ecosystem push (cargo/crates.io), and a measured win — Rust compiled to WebAssembly making a source‑maps implementation markedly faster and more consistent — letting the reader judge tradeoffs in ergonomics, safety, and productivity.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:06A Tale of Two Asyncs
- 7:33The Paradigm Paradox
- 14:10Solution 2.2b: Node.js Event Loop
- 31:08Stroustrup's Rule
related talks
46mA Tale of Two Asyncs
26mJavaScript Won the Web, Rust Is Taking the Critical Path
53mOpening Keynote with Carl Lerche and Alice Ryhl
29mAsychronous programming in Rust
36m10 Years of Rust: Why?
01h 42mGo Vs Rust Round Table
30mUnderrated gems of Rust & WebAssembly: Errors, Async, I/O
53mRust: Reach Further!