Industrial Strength Laziness: What's Next?
summary
Argues that Haskell moved from a niche idea to industrial-grade tools and now needs better interactive tooling: concrete proposals include richer Haskell Language Server editor actions (hole-filling, scoped generators), incremental type checking and parsing so feedback latency depends on edit size, practical debuggers tied to lazy abstract machines, and editor-aware use of type-class laws and program calculation. Describes foundation projects: CI for GHC, a searchable GHC error index with codes, and a security advisory database. Notes evaluation hurdles (expensive user studies) and suggests measurable benchmarks (edit-distance, latency, refactoring soundness).
AI-written summary · about
chapters (15)
- 0:00The Haskell virtuous cycle
- 1:35Haskell's journey
- 3:35The future of development
- 7:13Importance of tools
- 9:24Challenges in tooling research
- 13:00Context-aware editing
- 17:13Incremental feedback
- 20:33Debugging in Haskell
- 25:56Type class laws
- 27:47Tooling for calculation
- 30:49Informative types
- 33:55Software engineering for Haskell
- 35:31Achieving greater impact
- 38:59The Haskell Foundation
- 45:15Q&A and collaboration
related talks
01h 11mHaskell in Industry: Expert Panel on Tooling, Teaching & Real-World Use
01h 04mNot-So-Boring Haskell
01h 22mHaskell for Everyday Programmers
40mWhat Haskell taught us when we were not looking
46mPainless software development with Haskell
14mImpressions of ZuriHac, and Why We Love (and Hate) Haskell
03mInterview
01h 26mReflections on Haskell@Meta