A Haskell enthusiast switches to AI, the community lynches him

A recognized contributor to the Haskell scene publicly explains why he now codes with AI. Reaction: social banishment, hate mails, and the community rediscovering its own slogan.

The context

Haskell - the purely functional, statically typed, academically renowned language - has long carried a half-serious slogan: "avoid success at all costs". The original idea was rather healthy: not compromising the rigor of the language to please the market. But the small community that revolves around it has historically been marked by fierce sectarian wars, where intellectual rigor quickly turns into ideological purity.

A well-known contributor has just paid the price. His crime: having publicly stated that he now uses generative AI for coding - including in Haskell - and that he derives a productivity gain from it that, in his opinion, does not compromise the quality of his code since the Haskell compiler remains the arbiter.

What happened

According to The Register, the reaction was not a debate: it was a barrage of fire. Hostile social posts, ostracization from several community channels, questioning of his past work. The anti-AI purists in the field demanded a public disavowal. The person concerned stood his ground by adding that the community was literally applying its own slogan to the letter: "avoid success at all costs", even when that success came from wider adoption.

Why this resonates with the Torvalds affair

This is the second strong signal in a week on the same fault line in open source:

• Linux side: Torvalds refuses to exclude AI from the kernel ("fork if you want a project without AI").
• Haskell side: the community harasses a member for saying he uses AI.

Two projects, two opposite responses. The difference is the size and maturity of the governance. Linux has a historical benevolent dictator who cuts short. Haskell is a horizontal ecosystem where social policing replaces technical decision-making.

What a dev should take away

Whether you use Copilot, Claude, Codex, or nothing at all, the real issue is the code that comes out of your chain. A Haskell patch that compiles, passes property tests, and satisfies domain invariants is a good patch - no matter who typed the characters. Refusing a tool on identity rather than technical grounds is choosing to stay small, and that's exactly what the Haskell community has been criticizing its own culture for twenty years.

Key takeaways

• The AI vs. open-source divide is becoming a real fault line in free software.
• Projects with strong governance (Linux) make decisions. Horizontal communities (Haskell) self-purge.
• For a developer, the evaluation criterion for a patch remains the patch, not its origin.