4 ms·
My #1 issue was I work at several sites and at home. I don't really use a laptop so I just use git as a single user. The package management was such that I coul
by baldfat 11y ago
My #1 issue was I work at several sites and at home. I don't really use a laptop so I just use git as a single user. The package management was such that I could never have the same environment in multiple of locations. Something would break and I spent more time fixing then doing.
- mcbuilder 11y agoThat was a problem commonly called 'cabal hell'. You can alternatively use the stack build tool, https://github.com/commercialhaskell/stack https://github.com/commercialhaskell/stack, which works by fixing package versions against stackage snapshots. Before using stack I was always afraid to come back to a Haskell project after a few months, since using stack that's not a problem. Also, you don't have to worry about different machines, because stack is ensuring that you have the pretty much same build environment (at least the Haskell packages will have the exact same version). Stack also recently added support for using Nix to solve the problem fixing non-Haskell dependencies for a project.
- baldfat 11y agoWell after the love affair I have with Racket wears off I just might try to start back up in Haskell. Thanks! Love the idea of using nix.
- rspeer 11y agoThis looks so much better than Cabal. Why have I never heard about it in all the guides and StackOverflow answers I've had to search through when trying to escape Cabal hell?
- koloron 11y agoThe project has existed only since last summer.
- koloron 11y agomcbuilder has already mentioned it, but I really want to emphasize that dependency management in Haskell is an entirely different story now with stack.