Why Programming Languages Matter
summary
Covers concrete claims and artifacts: seven languages touched (not six), a working Eden preprocessor that hides network packing, an Emerald implementation with location-independent invocation that runs local calls about as fast as C and remote calls ~100× faster than Eden, the persistence of distributed GC problems, the immutable objects design for cheap replication, traits plus a trait browser that enabled reuse and won a test-of-time award, Grace/minigrace used for teaching. Emphasis is on what was built, measured, and which ideas actually changed practice.
AI-written summary · about
chapters (19)
- 0:00Welcome
- 0:26Why PL research matters
- 3:37PL as thought and magic
- 5:42How languages shape thought
- 7:50New languages change brain
- 9:34Recommendations for programming language exploration
- 12:20Personal PL design history
- 13:20ALGOL 68 influences
- 19:003R language design
- 28:39Eden project overview
- 32:34Emerald OOP distributed
- 37:53Emerald innovations
- 40:41Traits and inheritance
- 46:24Language design principles
- 47:51Why PL design is hard
- 49:14Closing thoughts
- 49:56Q&A: Effect systems
- 51:21Q&A: Design vs tooling
- 54:08Q&A: Teaching paradigms
related talks
06mHow We Used To Be
01h 05mFour Languages from Forty Years Ago
50mHow JavaScript Happened: A Short History of Programming Languages
40mAll of this has happened before, and it will all happen again.
44mThe evolution of a language
01h 02mWorse Is Better, for Better or for Worse
51mA history of computer programming
48mThe Graveyard of Good Ideas