Scarf Reluctantly Moves Away from Haskell After 7 Years Due to AI

Scarf has moved away from Haskell

After seven years running Scarf on Haskell, I have made the difficult decision to migrate to Python. While Haskell's type system proved reliable, its slow compilation times have become a critical bottleneck in an AI-driven development workflow. With LLMs generating code in minutes, the long wait for builds hinders parallel experimentation. Switching to Python has dramatically accelerated our feedback loops, allowing us to ship fixes instantly without sacrificing our high test coverage.

"If an agent can draft a plausible change in minutes and then spends even 15 minutes waiting for the project to build from a cold start, the compiler has now moved from being a papercut to being the dominant cost of that thread of work."