Story
After 7 years in production, Scarf has reluctantly moved away from Haskell
1 report
1 website
1 discussion
Latest report
Overview
Scarf has transitioned away from Haskell after seven years of production use. The decision reflects challenges faced while using Haskell in their development process.
Summary from avi.press.
Reports
One report so far. Additional coverage will appear here when it is linked to this story.
Community reactions
Each reaction summarizes sampled comments from the linked discussion.
Hacker News · avi.press
Hacker News discussion ↗
Historical count: 5 · 5 saved in sample · Historical sample
Analysis ready
Read this discussion’s reaction
Based on 5 sampled comments from this thread. Analyzed 2026-07-11.
- Praise: The combination of LLMs and Haskell is yielding impressive productivity, especially with type systems that provide vital feedback during development.
- Praise: Haskell's expressiveness and strong type system seem to help agents converge quickly to functional code, making it a powerful choice despite compile time issues.
- Praise: Some developers argue that Haskell's compile-time checks make it easier to catch errors, which is crucial when using LLMs for code generation.
- Concern: The slow compile times of Haskell are a significant hurdle, especially for iterative development with LLMs, making it less viable for fast-paced environments.
- Concern: Critics highlight that relying solely on LLMs could lead to overlooking valuable compile-time checks, undermining the quality of generated code.
- Concern: Some users feel that the author’s decision to move away from Haskell indicates a troubling shift away from strong type systems that help constrain LLM outputs.