--- title: After 7 years in production, Scarf has reluctantly moved... description: After 7 years running Haskell in production at Scarf, the founder explains why they reluctantly migrated to Python. The core driver was AI-assisted... canonical: https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: After 7 years in production, Scarf has reluctantly moved away from Haskell | daily.dev og:description: After 7 years running Haskell in production at Scarf, the founder explains why they reluctantly migrated to Python. The core driver was AI-assisted... og:url: https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof og:image: https://api.daily.dev/og/posts/Z5n4MnAOf.png og:image:alt: After 7 years in production, Scarf has reluctantly moved away from Haskell og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # After 7 years in production, Scarf has reluctantly moved away from Haskell **[Hacker News](https://daily.dev/sources/hn)** · 11 min read · 1 upvotes · 0 comments ## Summary After 7 years running Haskell in production at Scarf, the founder explains why they reluctantly migrated to Python. The core driver was AI-assisted development: LLM coding agents need fast feedback loops and cheap disposable execution contexts, but Haskell's slow cold build times and complex toolchain (Nix, caches, CI setup) became a dominant bottleneck when running multiple parallel agents. The post argues Haskell's type safety advantages are partially offset by LLMs catching errors at code-generation time, and that the Haskell community's resistance to AI workflows risks the language's long-term relevance. The author calls on the Haskell Foundation to prioritize build speed, onboarding, documentation, and agent-friendly tooling over type system research, warning that Haskell is not accelerating alongside other ecosystems in the AI era. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why would a company move from Haskell to Python for AI-assisted development? Long Haskell compile times and ecosystem friction around caching, Nix, and CI became a major bottleneck once teams started running multiple AI coding agents in parallel. Cold builds and cache setup impose a repeated tax on every new worktree or branch, whereas Python's faster iteration loop fits the disposable, parallel execution style agents need, making the switch worthwhile despite losing static type safety. _Anyone weighing a language switch for AI-agent workflows can track real-world migration experiences like this on daily.dev._ ### Does giving up Haskell's type safety cause problems when moving to Python with AI-generated code? Not noticeably so far, according to one company's seven-year production migration. Improved test coverage, driven largely by AI-generated tests, has compensated for the loss of compile-time guarantees, and bugs that do surface get hotfixed much faster than before, since fixes can ship within minutes of being reported. _Developers debating type safety versus AI-driven test coverage can follow real migration stories on daily.dev._ ## Similar posts on daily.dev - [Enterprise Haskell at H-E-B](https://daily.dev/posts/enterprise-haskell-at-h-e-b-sjpe3tn1b) · Lobsters · 0 upvotes · 0 comments - [Fragments: May 14](https://daily.dev/posts/fragments-may-14-lvinaemdo) · Martin Fowler · 1 upvotes · 0 comments - [“I started to lose my ability to code”: developers grapple with the real cost of AI programming tools](https://daily.dev/posts/i-started-to-lose-my-ability-to-code-developers-grapple-with-the-real-cost-of-ai-programming-tool-2ysnnh7pi) · The New Stack · 2 upvotes · 1 comments --- Tags: [#python](https://daily.dev/tags/python), [#ai-coding](https://daily.dev/tags/ai-coding), [#haskell](https://daily.dev/tags/haskell) [View this post on daily.dev](https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"After 7 years in production, Scarf has reluctantly moved away from Haskell","url":"https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof"},"datePublished":"2026-07-10T14:37:03.456Z","dateModified":"2026-09-14T06:12:49.895Z","description":"After 7 years running Haskell in production at Scarf, the founder explains why they reluctantly migrated to Python. The core driver was AI-assisted...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9848a2dc4a2e94ea7f29f16917254c04?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9848a2dc4a2e94ea7f29f16917254c04?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,ai-coding,haskell","timeRequired":"PT11M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"After 7 years in production, Scarf has reluctantly moved away from Haskell"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell-z5n4mnaof#faq","mainEntity":[{"@type":"Question","name":"Why would a company move from Haskell to Python for AI-assisted development?","acceptedAnswer":{"@type":"Answer","text":"Long Haskell compile times and ecosystem friction around caching, Nix, and CI became a major bottleneck once teams started running multiple AI coding agents in parallel. Cold builds and cache setup impose a repeated tax on every new worktree or branch, whereas Python's faster iteration loop fits the disposable, parallel execution style agents need, making the switch worthwhile despite losing static type safety. Anyone weighing a language switch for AI-agent workflows can track real-world migration experiences like this on daily.dev."}},{"@type":"Question","name":"Does giving up Haskell's type safety cause problems when moving to Python with AI-generated code?","acceptedAnswer":{"@type":"Answer","text":"Not noticeably so far, according to one company's seven-year production migration. Improved test coverage, driven largely by AI-generated tests, has compensated for the loss of compile-time guarantees, and bugs that do surface get hotfixed much faster than before, since fixes can ship within minutes of being reported. Developers debating type safety versus AI-driven test coverage can follow real migration stories on daily.dev."}}]} ```