A Tale of Two Asyncs
summary
Argues that Node aims to be a purely evented nonblocking runtime while Rust explicitly targets systems‑level, memory‑safe server code; details Rust’s async stack—mio futures tokio—and cites a real example where Rust→WASM rewrote source‑maps and ran faster without becoming unreadable, and Servo cut C++ from ~160K to ~85K lines; notes the async/await RFC draws intense review—258 comments—and shows the designs land but demand heavy community coordination.
AI-written summary · about
chapters (24)
- 0:00Start
- 2:09Rust Bridge
- 3:50Philosophy Genealogy
- 5:27The Structure of Scientific Revolutions
- 6:07What Is the Best First Programming Language
- 6:52Programming Paradigms
- 7:30The Paradigm Paradox
- 12:10The Reactor Pattern
- 14:02Type of Language Does Javascript Want To Be
- 15:42Russ Compiler
- 15:53The Rust Compiler
- 17:09Domain Working Groups
- 18:15How async Works in Rust
- 19:10Should You Write a Web Service with a Systems Level Language
- 22:38Developer Experiences
- 23:36Stages of Learning
- 23:53Three Stages of Learning
- 26:28Stack Overflow Survey
- 30:47Lazy Consensus
- 32:04Scratching a Developer's Personal Itch
- 32:18The Roadmap Process
- 41:46Feature Uniformity
- 42:10Language Complexity
- 42:54Conclusion
related talks
47mA Tale of Two Asyncs: Open Source Language Design in Rust and Node.js
29mAsychronous programming in Rust
26mJavaScript Won the Web, Rust Is Taking the Critical Path
18mA better way of doing Async Rust
53mOpening Keynote with Carl Lerche and Alice Ryhl
36m10 Years of Rust: Why?
26mReasoning with Async Rust
30mUnderrated gems of Rust & WebAssembly: Errors, Async, I/O