@gon782 I recently came across the following talk:
which was very interesting, since it brings up some important points about the Haskell development environment that could be improved;
some quick examples being:
- The learning cliff.
- There are too many libraries, so it is difficult to find good/maintained libraries that do what you want between the cruft.
- The Haskell community is divided about a couple of core issues, such as if it is better to manage your dependencies (and even ‘how to install Haskell’) using Cabal or Stack.
- Some libraries make odd choices of when to use partial functions, and when this inevitably does bring down your application, the error messages are extremely cryptic and there usually isn’t a stacktrace at all.
Besides this, the talk also talks about web-development-specific things, where their team had issues changing their Rails-mindset to a Haskell one. (And even though it has been a year, in my personal opinion, some of that Rails mindset still shines through in what they attempt to do in Haskell, but most of their points are very valid and definitely interesting to hear).
I really like what you’ve written in your latest post, by the way. I couldn’t have said it better 
.
