How to answer "why will yours succeed, when X, Y, and Z have failed?"
summary
Predicts adoption with three concrete design requirements: a clear value that fixes known pain (examples: TypeScript adds static typing to JavaScript), broad availability by targeting where the old tool already runs (cfront → C, TypeScript → JS, Swift via Xcode), and high-fidelity compatibility so old projects can use new code side-by-side or gain benefit from one line of code. Historical data shows ~10,000 languages created but only hundreds survive and compatibility gaps typically add ~10 years to adoption (Python 3, C99, C++11 string ABI).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:30What is a new thing
- 5:50How many programming languages
- 8:20The valley proposition
- 12:30The counterexample
- 16:15Question
- 18:10The Holy Grail
- 20:05Portability
- 29:03Aviation example
- 30:47Programming languages
- 36:00Python
- 37:31C99
- 38:45C Compatibility
- 40:16Backward Compatibility
- 41:26Compatibility Pitfalls
- 44:04Safe Sea Dialects
- 46:15The same code means something different
- 47:24Why will yours succeed
- 48:40A successor to C
- 51:11How to answer
- 57:09Epochs
related talks
36mWhen to be Weird
01h 30mThe Past, Present and Future of Programming Languages
01h 02mFear: The Role of Fear in Language Adoption
01h 03mWhy the Next Five Years Will Be About Languages
35mSoftware Engineering - Development in 100 Years Time
52mThe Past, Present and Future of Programming Languages
10mpart6 – Ted Neward
56mThe Past, Present & Future of Programming Languages