Is there an idiomatic Haskell?

There is not an idiomatic Haskell, and I think initiatives to codify a “simple Haskell” or “common Haskell” have stalled out. The best advice I’ve seen is to cultivate an engineering dialect almost as part of your business strategy. For example, Obsidian Systems’ strategy appears to be “build the biggest, most powerful levers you can and apply them to the problem”, which is why they’re deep into things like Nix and Reflex. The tools you reach for will be determined in part by how you plan to hire, and how long you’re willing to spend onboarding as you expand. I wrote up a few idioms we use at work: Some Haskell idioms we like. I also maintain a list of libraries I like. It’s not nearly complete enough to build a coding standard around, but might be helpful: Haskell (Libraries) | Wiki | jackkelly.name. I find the type-level “big guns” (like package singletons) usually start to creep in when I try to use types to nail down the last 10% of a problem. Often, 80% correcteness is significantly simpler to write and maintain, and still leagues ahead of many other languages.