Haskell in Industry: Expert Panel on Tooling, Teaching & Real-World Use
summary
Panelists report more people are paid to program Haskell now than a decade ago, with growth concentrated in smaller companies and long‑lived shops (one startup grows to 15–16 Haskell engineers). Concrete pain points are tooling, onboarding, divergent libraries and extensions, and adding Haskell to large centralized infra (a big company decommissions a project). Practical fixes tested: standard rows of extensions and packages, code‑review driven style, and an LLM layer over GHC for friendlier errors. Domains that actually win: concurrent network services, web backends, DSLs and heavy testing.
AI-written summary · about
chapters (15)
- 0:00Haskell in Industry panel intro
- 7:03Haskell growth in industry
- 14:29Haskell hiring and stability
- 18:26Why adopt/abandon Haskell
- 25:16Domains where Haskell excels
- 28:47Haskell in small companies
- 31:40Haskell community strengths
- 32:23Rust migration from Haskell
- 36:13Haskell foundational improvements
- 40:04Assessing Haskell skills
- 44:14Standardization vs experimentation
- 51:35Haskell tooling best practices
- 57:55Haskell in non-Haskell companies
- 1:02:52Haskell in education
- 1:08:53Closing remarks
related talks
47mIndustrial Strength Laziness: What's Next?
03mInterview
51mWhy Do Companies Stop Using Haskell?
01h 22mHaskell for Everyday Programmers
40mWhat Haskell taught us when we were not looking
01h 26mReflections on Haskell@Meta
01h 04mNot-So-Boring Haskell
53mFalling Skies: Haskell Tooling and Ecosystem Growth