Tony Morris

it's just experience: "hey Brian so I tried to use Stack and I'm getting this weird problem..." over and over and over

This is all just too vague. An opinion shared by many would get me using Scala over Haskell, so I'm not sure what to do with that. And I've not had much of "some weird error" with Stack for a while now. Did no one track it down? I mean cabal new-build is finicky still too.

> An opinion shared by many would get me using Scala over Haskell ? Many people think things about Scala. They are all wrong. Surely you know that. Most people who know Scala well, no longer use it. Why is this? Why don't you hear of it? Follow the analogy. Watch your bias.

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?

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.