Keynote: If at first you don't succeed (..)
summary
History lesson: Erlang starts as an Ericsson in-house tech, gets open sourced Dec 1998 after an internal ban, and later shows commercial exits—Bluetail → Altean (~$152M in shares) and Tail‑f → Cisco (~$175M). Claims: Erlang’s VM gives live code upgrades and massive concurrency but OTP is harder than the language. Pain points: training cadence (weeks → months), ecosystem tooling, and hot code loading lost in containers unless extra work is done. Adoption tactics: start small, use volunteers, build grassroots references, and plan for staff churn.
AI-written summary · about
chapters (14)
- 0:00First Some History
- 0:39Why Erlang was Invented
- 4:41Two Projects
- 6:24What happened?
- 9:05Trying to Market SW Technology
- 15:31Morals of the story
- 20:30The Disguised No's
- 25:18The Easy Cases are Rarer
- 28:26Commoditization
- 31:12Choosing Projects
- 34:59Build from Grassroots • Managers are dying to find ways to get their employees to do what they
- 36:58How do we hire for this?
- 39:47Fred's experience, quickly
- 41:16Questions?
related talks
01h 00mKeynote: Over a Century of Programming
59mKeynote: Elixir Should Take Over the World
57mMaximising Side Effects When Adopting Functional Programming
45mKeynote: One Monolith, Many Teams: Growing an Org...
39mThings that Matter
08mTalks with Brian Troutwine
20mKeynote: From Prototype to Innersource to Open Source: Lessons...
33mHigh availability with Elixir and Erlang