Keynote: Over a Century of Programming
summary
Claim: Erlang emerges from practical telco needs for fault‑tolerant, hot‑upgradeable, distributed systems and proves that by building and iterating real artifacts. Implementation path: a Prolog prototype then a C runtime (JAM → BEAM) and OTP libraries; experiments show interpreter speeds ~245→283 reductions/s and earlier 35/s compiles, while products like the AXD301 switch and mobility servers ship and run; corporate ban leads to open source adoption and broad ecosystem growth.
AI-written summary · about
chapters (5)
- 0:00Start
- 11:39If the hardware doesn't change the software won't change
- 40:58AXD 301 is a great success...
- 42:04BANNED
- 48:27The Future
related talks
51mKeynote: If at first you don't succeed (..)
59mKeynote: Elixir Should Take Over the World
57mMaximising Side Effects When Adopting Functional Programming
20mKeynote: From Prototype to Innersource to Open Source: Lessons...
39mThings that Matter
33mHigh availability with Elixir and Erlang
45mKeynote: The Hitchhiker’s Guide to the Unexpected
08mTalks with Brian Troutwine