"Breaking the Legacy: A New Era of Programming Language Design"
summary
Argues that languages must be built around the actor model with message passing, no shared memory, and capability-based security; specifies three capability origins: creation, transmission, introduction and uses proxies for revocation. Describes a transitional language called Misty (design at mistiesystem.com) that strips JavaScript to a safe subset, adds actor addresses and blobs, removes exceptions, and targets an x64 code generator (bootstrapped in JavaScript). Claims this is vaporware but presents concrete semantics: queued messages, single-turn execution, and the principle of least authority.
AI-written summary · about
chapters (22)
- 0:00Introduction to legacy languages
- 2:18Generational language evolution
- 5:31Limitations of single-machine models
- 7:11Introducing the actor model
- 9:49Actor system recommendations
- 12:08Performance in distributed systems
- 16:51Pipelining with actors
- 21:07Security through capabilities
- 24:59Modularity and maintainability
- 26:48Introducing Misti language
- 30:21Q&A session begins
- 31:24Revocation in actor model
- 33:32Performance myths and efficiency
- 35:16Why actor model isn’t mainstream
- 37:05Misti implementation details
- 38:31Patterns over languages
- 40:27Human-centered language design
- 41:34Why now for the actor model
- 42:16Handling shared information
- 43:44Career-defining decisions
- 45:10Creation of JSON
- 47:14Closing remarks
related talks
57mWhy Programming Languages Matter
50mThe Post JavaScript Apocalypse
36mThe Power of the Paradigm
01h 04mThe End Of Gen. Purpose Languages-Rubinius 3.0+The Next 10 Mil. Programs
10mpart6 – Ted Neward
10mpart4 – Ted Neward
59mWhy the Next Five Years Will Be About Languages
22mA Vision of Miking: Interactive Programmatic Modeling, Language Composition, and Compilation