i think @GabrielG439 said this in a talk once and i've found it a useful thing to remember sometimes:
> Cabal was built for managing packages (a single package) whereas Stack was built more for managing *projects*, that is, a collection of packages
-
The root problem here is that neither Stack nor Cabal had a formal requirements gathering phase like Nix did in Eelco's thesis. As a result, nobody can say for certain whether Stack/Cabal "work" if there is no specification for what it means for them to "work"
I would really like there to be zero, or even just small, practical penalty on me, and students, for the existence of stack. Consistent failure to acknowledge the cause of this ongoing penalty, is quite frustrating. it is *so* predictably consistent. Hence, fuck stack.
-
-
I tried to get the let's lens course working without stack (I'm on nixos) but I couldn't. Are there some instructions somewhere about how to do that?
-
Haven't tried in years, but I just now successfully did: cabal sandbox init && cabal install --only-dependencies && cabal repl I intend to update that repository in the next few weeks with better material (and nix).
- Show replies
New conversation -
-
-
I’ve been able to help folks with pretty Much any not a bug cabal issue for like forever. Modern cabal makes it a dream :)
-
Yeah, but what if a keen beginner has fallen into the trap of using stack? Now they are stuck, because stack. How do you break the news?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.