Stack has three things I find useful for teaching: one tool for everything, a "new" scaffolding, and --file-watch.
@dibblego lobbied against monolithic tools (so ghcid instead of --file-watch), but this to me is a professional Haskell concern, not someone just learning fresh.
-
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.
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.
-
-
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
-
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?
- 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.