Why Programming Languages Matter
summary
Over forty-five years work on six languages yields concrete lessons: a small preprocessor (EPPL) hides packet packing and makes distributed code usable, Emerald implements immutable objects and location-independent invocation so local calls run about as fast as C and remote calls run roughly 100× faster than earlier prototypes, traits simplify composition only with a navigable browser, and Grace plus minigrace proves a web-delivered teaching environment can actually scale — tooling and measurable performance decide adoption, not sloganized paradigms.
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
01h 30mThe Past, Present and Future of Programming Languages
01h 03mWhy the Next Five Years Will Be About Languages
56mThe Past, Present & Future of Programming Languages
01h 10mThe Past, Present and Future of Programming Languages
52mThe Past, Present and Future of Programming Languages
49mWhat Counts as a Programming Language?
59mWhy the Next Five Years Will Be About Languages
43mA whirlwind tour of my favorite programming languages