5 ms·
I think Haskell tooling is pretty good now. VSCode with the Haskell plugins is simple to setup. I used to use Emacs for Haskell, but the VSCode support is now s
by mark_l_watson 6y ago
I think Haskell tooling is pretty good now. VSCode with the Haskell plugins is simple to setup. I used to use Emacs for Haskell, but the VSCode support is now so good that I just take the easy route.
Stack and stackage made package management much easier for me. I am an enthusiastic, but not great Haskell programmer so I like running the ‘hlint’ linter program for hints on improving my code.
My heart is really with Common Lisp, but Haskell is also a pleasure to use and the tooling seems much better to me than five years ago.
- metreo 6y agoI think Haskell versioning is highly bifurcated.
- codygman 6y agoYou mean like SemVer vs the default whose name I can't remember?
- metreo 6y agoI mean like installing and managing multiple versions of the compiler toolchain is painful.
- sullyj3 6y agoI mean, it's all pretty well automated by stack, the only painful part is that it can take a long time and use a lot of storage.
- metreo 6y agoSure it's pretty well automated, but not a great experience.
- tome 6y agoIs there something about ghcup that doesn't do the job for you? You ask it to install a particular version of GHC and Cabal for you. It does it. Multiple versions can exist together. Job done. https://www.haskell.org/ghcup/ https://www.haskell.org/ghcup/
- shirogane86x 6y agothe default is pvp [1] and I think most packages use that and not SemVer? or, at least, I can't remember off the top of my head of specifically pinning a package with SemVer. [1] https://pvp.haskell.org/ https://pvp.haskell.org/