Managing externalities in a functional world
summary
Summarizes evidence from a 1994 military study and a 2004 survey of seven adoption inhibitors to argue that adoption hinges on nontechnical factors as much as on language features. Notes that Elixir already solves many technical blockers: Hex packages, Nerves for embedded, Docker and Homebrew installs, and C bindings via NIFs. Recommends concrete actions: build an end to end prototype to cut implementation risk, invest in commercial support and training, and cultivate killer apps plus reproducible docs to scale beyond a niche.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:06Outcome: Dramatic FP Edge
- 4:207 Adoption Inhibitors
- 7:54Technical Inhibitors vs Elixir
- 9:37How To Sell Elixir [2017]
- 14:52Possible Future 1 of N
related talks
57mMaximising Side Effects When Adopting Functional Programming
39mFunctional Architecture for the Practical Rubyist
31mBuilding a Sustainable CodeBase with FP
39mFunctional Programming And the Real World
44mReal-World Functional Ruby
23mHow to teach Elixir to non-functional developers
01h 03mKeynote panel discussion: The next 30 years
47mThe Tension Between Expediency and Correctness