{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig7srrzo3twmvuewpjt76rkilndbqcqimhys6r433oj24zkg5xa3a",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mgnklsoy5c42"
  },
  "path": "/t/haskell-vibes-jappie/13772#post_18",
  "publishedAt": "2026-03-09T15:33:50.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "MangoIV:\n\n> I ask you, can you justify writing Haskell at all? Why would you not write Javascript? LLMs write it faster and better, it doesn’t matter how many abstractions we are missing, it’s all `foldr` anyway!\n\nThe article does address this - the Haskell that the AI slops together is way easier to verify than the JS it can make. Due to Haskell. Specifically due to Haskell’s rigorous underpinnings.\n\nI do think this AI stuff has made it more clear than ever to me that there is a fork in Haskell thinking. There’s the static types and there’s the functional programming. The AI-maxxers are _very into_ the static types.\n\nBut before AI, a lot of them were already into that. They were managers or staff engineers and instead of wrangling AI, there were wrangling org charts of fungible humans. In both cases, the ethos is “how do we get this thing to do a good job building the stuff falling down the waterfall without trusting it?” It is no surprise to me that AI is taking off in industry. Nobody built software well in industry anyways, and now they can convert their money into bits cheaper. With fewer dependencies on humans with agency.\n\nThe functional part of Haskell feels like it’s getting lost. The AI code I see is so low-level. It’ll freely just write some direct recursion or a hacky fold. But it’ll write a doc comment! Should we do better? idk. But a single diff of that code looks fine. A couple years of diffs of those and the codebase is soup.\n\nI fear the day when we start linting to optimize code for AI consumption and editing. I’m sure it’s coming. We already format our code to minimize `git diff` changes due to whitespace at the cost of human readability. There’s a general problem where engineers let their tools drive their code, and it only gets worse as the engineers get more meta and the tools get more powerful.",
  "title": "Haskell 💜 Vibes / Jappie"
}