For what it's worth, I've been using Haskell in production at Bitnomial, a financial exchange, and LLMs + Haskell is an extremely productive combo.
Since Opus 4.6, LLMs have been pretty clever at using fancy types with libraries like Servant and Beam. The expressiveness of the types, combined with feedback from the compiler, means that agents converge quickly to something that works. I don't think I've noticed agents having to run the compiler so often that compilation speed is an issue.
Chair of the HF here -- things are going quite well, actually. We have great sponsors who come back year after year, the HF has been spending more to make infrastructure more reliable (e.g. for Hackage), and we've started a new event series focused on North America (https://haskell.foundation/events/2026-amerihac.html), which has been a great success!
Our metrics are also showing that Haskell usage is actually growing. So overall, can't complain!
For example, one thing that is a friction point at my own job is knowledge of tooling for performance tuning and optimization. It's not that Haskell doesn't have this tooling, it's just not well-known.
Chair of the Haskell Foundation here -- funny to see this on the HN front page!
Not mentioned in the update is that the Haskell Foundation is moving towards a model that already exists within the OCaml Foundation. The HF and OF have the same challenge: a shallow pool of (relatively) large sponsors.
Of course big successful firms have more money to contribute, and we are thankful for them. This move, whereby the HF will deploy more of its financial resources on technical challenges directly, is meant to attract the other 99.9% of firms using Haskell in production. Many firms, including my own employer, have a more tit-for-tat view of sponsorship.
If you have thoughts, or would like to get involved, do not hesitate to reach out to me! E-mail in bio
I will die on this hill: tech firms that mandated 5 days in the office was about soft layoffs, rather than a principled stance on individual performance under WFH.
My "evidence" is that trading firms that kept raking in the money, and that benefit from maximum productivity of their employees, still generally have a hybrid work culture.
This is the first release of any Haskell debugger, as far as I know. It coincides with the release of v9.14 of the de-facto standard Haskell compiler, GHC
As others have pointed out, the monthly Who Is Hiring and Who Wants to be Hired threads are a good place to start.
Since you probably don't have industry experience, I strongly suggest you build a good Github profile. Build your own software in public, contribute to projects. That's an excellent hiring signal
I'm particularly excited by the prospect of bringing together the ecosystem of data science tools, with Cloud Haskell[0]. There's no reason the Haskell community can't have something like Dask or Ray, but with Haskell's stellar type system.
That is a really tough spot to be in. I don't know of any content that's aimed at someone like you.
You might be interested in reading the Monday Morning Haskell blog[0] series, which presents examples of how to do certain tasks in Haskell. See [1] for an example.
I'm switching from VSCode as well. I love Helix's (and Kakoune's) editing model centered around selections rather than motions. I can see what I'll operate on interactively.
I still use VSCode when navigating complex codebase changes, just because of the visual file tree. I hope to fully switch over soon.