4 ms·
I’m a relative newcomer to Haskell. I still haven’t used it for anything serious, but I’d like to. I had experienced all of these problems. Initially, I was at
by madmax96 6y ago
I’m a relative newcomer to Haskell. I still haven’t used it for anything serious, but I’d like to.
I had experienced all of these problems. Initially, I was attracted to Haskell for the promise of “if it compiles then it’s probably correct.” I quickly discovered that isn’t true, for the reasons discussed in the article.
But I also had issues with Cabal. I couldn’t get Snap to install. I tried installing it in a container, still didn’t work. I finally figured out something that would let me build with Snap, but for some reason LSP in Emacs couldn’t find the snap libraries, so it couldn’t provide me correct feedback. And then the build times. Wow. I gave up on writing that program in Haskell and wrote it in Go instead.
I think Haskell has a lot to offer. I’d be open to trying it again. Hopefully these shortcomings improve.
- marcosdumay 6y agoHaskell has a real tooling problem. At this point, I do not allow any Haskell IDE engine to manage project data. Things work much smoother if you call cabal directly. But that's actually a low ball. I don't let any Java or Javasript, or Python (except Conda) IDE manage it either. And, of course, I've long gave up on anything integrated for C, C++ or Perl.