I'm just saying if it's a technical problem, then explain it to me technically. I don't know why I need to worry about who holds what opinion.
-
-
Replying to @shajra @puffnfresh and
1. Stack causes more than zero problems. 2. Stack demonstrates no practical benefit. Ergo, Stack is a net penalty. It's not a trade-off. QED. You probably disagree with (2), in which case, demonstrate otherwise. No vagueness.
1 reply 0 retweets 0 likes -
Stack - manages ghc versions for projects - provides automatic sandboxing with dependency sharing where appropriate - handles git dependencies - file watch is useful, even when ghcid is available
2 replies 0 retweets 4 likes -
Replying to @mattoflambda @shajra and
All of these were solved problems before stack existed. What is it do you think we were doing all those years? Waiting for this groundbreaking thing called stack?
1 reply 0 retweets 0 likes -
I have no idea what you or anyone else was doing before stack, because the instructions given to beginners were fraught with problems that stack solved. As far as I know, cabal hell was a common experience.
2 replies 0 retweets 4 likes -
Replying to @mattoflambda @dibblego and
Cabal does not handle git dependencies. What tool are you thinking of?
1 reply 0 retweets 1 like -
Replying to @mattoflambda @shajra and
I WAS USING HASKELL BEFORE CABAL EXISTED. CAN WE PLEASE NOT MAKE THIS STACK V CABAL. PLEASE PLEASE PLEASE.
1 reply 0 retweets 1 like -
-
Replying to @TheWizardTower @mattoflambda and
Either honesty, or I'm going to take the piss.
1 reply 0 retweets 0 likes -
Replying to @dibblego @mattoflambda and
*looks over thread* I think you hit that mile marker already.
1 reply 0 retweets 0 likes
Replying to @TheWizardTower @mattoflambda and
Nautical mile or statute mile?
11:23 PM - 4 May 2018
0 replies
0 retweets
0 likes
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.