This is maybe a big ask, but could anyone who has been a long time Haskell user give some bullet points on major language developments since ~2015 or so?<p>I was deep into Haskell and used it as my primary language from 2012-2015, but switched over to Rust around that point. I've been thinking about trying a mid-size hobby project in Haskell to get updated on the new state of the art.<p>Some things I have heard tangentially (and may be misremembering):<p>- Field accessors (i.e. `myObject.field` instead of `field myObject`)<p>- Monad hierarchy refactoring (monad of no return)<p>- LiquidHaskell making some inroads<p>How is package management these days? Is cabal hell still a thing? How's the IDE situation?
I'm a relatively newcomer so maybe discard this comment. What hurts me most at this point is the lack of documentation, or at least the lack of simple examples. This is the only language I know where more often than not the main documentation of a module is a link to a journal paper. Alternatively, I'm just not always able to infer what a function does just by looking at its signature. Just give examples.
I have tried to push for a Haskell in my previous job. We had a task that was especially well suited for that. It was a large collection of mostly declarative computations for the mixed-integer optimization. I also wanted to take an advantage of Liquid Haskell since that would allow us to move a few checks from runtime to compile time. That would be a game changer. Things like divide by zero were very common. It is easy to detect division by zero but not so easy to cover all the edge cases that could cause it.<p>At the end of the day we did not go forward with that. The reasons mostly were:<p>1. Even though I used a lot of my "social credit" on this everybody was scared of it. Mostly because of the vibe that comes with Haskell.<p>2. Purely functional languages come with lots of concepts that are unfamiliar to most programmers (everybody in my team was well equipped with CS degree and theoretical knowledge but still those concepts were new-ish).<p>3. The higher in company hierarchy the more people were scared (this was a critical project for the whole company of ~22k people).<p>4. We couldn't figure out debugging. Our codebase was ~40k generated lines of code (type definitions, basic accessor functions and so on) plus ~10k LoC we would write on top of that. The only VSCode-based debugging I was able to figure out was basically loading it in GHCi and then doing the debugging which was fine. The problem was the load itself. It took ages because it recompiled majority of the codebase on load. No precompiled parts were used. Result was that every debugging session took minutes to start up.<p>On the other hand Liquid Haskell has a great potential and I hope that there is a future in which we have similar tools in more common languages. As the complexity of the codebase grows it become more important to have a tool to provide additional guarantees. We did not have much of the code on its own but it was packed with complexity and dependencies. Liquid Haskell seemed to provide a tool that does not get into your way when you don't need it but it available when you want it.
I hope tooling becomes the #1 priority.
- after using languages like Rust and Elixir, It's hard going back to other langs where the tooling is not at that standard,
I really wish I could use Haskell all the time instead of Python and the most dreaded programming language, a.k.a. MATLAB.¹ I guess all that's left for me is to do whatever toy projects come to my mind in my free time.<p>¹ <a href="https://survey.stackoverflow.co/2022/#most-loved-dreaded-and-wanted-language-love-dread" rel="nofollow">https://survey.stackoverflow.co/2022/#most-loved-dreaded-and...</a>
As a non-Haskeller, the only tool I can think of interacting with that has any Haskell is Hasura's graphql-engine[0], which GitHub stats say is 28% Haskell (and then like 55% web languages, so I assume the backend is all Haskell and the web languages are for the UI it presents etc)<p>Are there other popular Haskell tools? Or is it more of an academic language? I was surprised to see it on the GitHub repo.<p>[0]: <a href="https://github.com/hasura/graphql-engine" rel="nofollow">https://github.com/hasura/graphql-engine</a>
There’s a bunch of issues with how these surveys have been designed in the past, imo, and generally solicitating easily interpretable qualitative responses on technical systems is just hard.