Re:A technical vision for the Haskell ecosystem
by ddellacosta on Friday November 13, 2026 @01:27PM
(#50487663)
> If I could have a vision for Haskell, it was for it to be useful.
...
> Haskell surely needs good DX, but it also needs really better reasons for existing.
Man am I tired of people dropping negative crap like this any time Haskell comes up, especially when they end up at the top of the comments. It ends up derailing most conversations about Haskell that aren't on explicitly Haskell-focused forums, and turns every post on Haskell elsewhere into a referendum on the language itself. FFS the post itself is explicitly about polishing up the technical infrastructure _to achieve what you're complaining Haskell doesn't have_ and all you can do is shit on Haskell in response: "We want to improve the developer experience!" You: "No one wants to use Haskell because the developer experience is so shit!"
Put your money where your mouth is and do the polishing you're complaining about if you actually give a shit about Haskell. Fucking make something! Nothing is stopping you. Haskell is useful right now. I have personally been building a home automation system for it that uses Lua, MQTT, STM, and more that I have been running nonstop in my home for literally years now and it's absolutely awesome to work on and it's rock solid--partially because Haskell does an amazing job of helping me avoid bugs and provides a wonderful refactoring experience, which is a huge part of its reason for existing thank you very much.
All comments like yours do is dissuade others from taking a look at the Haskell ecosystem by implying it's a pointless language; it steers people away, as the main takeaway is that you can't actually build stuff in Haskell and so why would you want to use a language that you can only build CLI apps in? (Absolute bullshit btw.) As someone that cares about Haskell and spends my time actually building stuff with it, I just read posts like this and shake my head. You absolutely can use Haskell to make things, and insofar as Haskell doesn't get used (distinct from being useless) and has a ton of sharp unpolished edges remaining, it's the fault of posts like yours as much as anything. Either get involved or give it a rest and go use the other languages you seem to prefer. You aren't treading new ground with this comment.
Sorry to swear so much but that really pissed me off
...
> Haskell surely needs good DX, but it also needs really better reasons for existing.
Man am I tired of people dropping negative crap like this any time Haskell comes up, especially when they end up at the top of the comments. It ends up derailing most conversations about Haskell that aren't on explicitly Haskell-focused forums, and turns every post on Haskell elsewhere into a referendum on the language itself. FFS the post itself is explicitly about polishing up the technical infrastructure _to achieve what you're complaining Haskell doesn't have_ and all you can do is shit on Haskell in response: "We want to improve the developer experience!" You: "No one wants to use Haskell because the developer experience is so shit!"
Put your money where your mouth is and do the polishing you're complaining about if you actually give a shit about Haskell. Fucking make something! Nothing is stopping you. Haskell is useful right now. I have personally been building a home automation system for it that uses Lua, MQTT, STM, and more that I have been running nonstop in my home for literally years now and it's absolutely awesome to work on and it's rock solid--partially because Haskell does an amazing job of helping me avoid bugs and provides a wonderful refactoring experience, which is a huge part of its reason for existing thank you very much.
All comments like yours do is dissuade others from taking a look at the Haskell ecosystem by implying it's a pointless language; it steers people away, as the main takeaway is that you can't actually build stuff in Haskell and so why would you want to use a language that you can only build CLI apps in? (Absolute bullshit btw.) As someone that cares about Haskell and spends my time actually building stuff with it, I just read posts like this and shake my head. You absolutely can use Haskell to make things, and insofar as Haskell doesn't get used (distinct from being useless) and has a ton of sharp unpolished edges remaining, it's the fault of posts like yours as much as anything. Either get involved or give it a rest and go use the other languages you seem to prefer. You aren't treading new ground with this comment.
Sorry to swear so much but that really pissed me off