Why Do Companies Stop Using Haskell?
summary
Analyzes why companies stop using Haskell by naming concrete failure modes—wholesale rewrites that trigger the second-system effect, fixed-term experiments that end when funding dries up, acquisitions and leadership swaps that strip political support, and replacements driven by trend-chasing or tooling gaps. Shows how maintenance is systematically undervalued, how some teams succeed by shipping a boring subset and funding tooling, and ends with career advice: preserve reputation, push for open source, and be ready to walk away when incentives break.
AI-written summary · about
chapters (17)
- 0:00Introduction And Motivation
- 5:02Haskell's Position In The Software Industry
- 7:43How Companies Make Technology Decisions
- 12:15Why Companies Choose Haskell
- 14:16Rewrites And The Second System Effect
- 21:16Experiments, Funding, And Failure
- 22:00Vanity Projects And Technology Choices
- 23:25Consulting, Clients, And Sustainability
- 24:34Acquisitions And Team Transitions
- 26:04Leadership Changes And Political Capital
- 27:05Trend Chasing And The Magpie Effect
- 28:45Complexity And Maintainable Haskell
- 30:17Scaling Challenges And Ecosystem Investment
- 33:21Career Strategy And Professional Leverage
- 35:14Unionization, Community, And Long-Term Thinking
- 37:03Why Haskell Is Still Worth It
- 39:31Audience Questions And Discussion
related talks
01h 11mHaskell in Industry: Expert Panel on Tooling, Teaching & Real-World Use
01h 04mNot-So-Boring Haskell
03mInterview
47mIndustrial Strength Laziness: What's Next?
42mIntroducing A Functional Language At Work
01h 26mReflections on Haskell@Meta
40mWhat Haskell taught us when we were not looking
01h 22mHaskell for Everyday Programmers