Tony Morris

Sure thing buddy. Yes, we were all tripping over ourselves, screaming "oh no, where is the saviour? We shall call it stack when it shows itself!" Yes, that is what we were all doing. *sigh*

It was painful. I was there before stack (but not before cabal). And it was painful. I managed to work around all issues. Yet much pain was involved. You're being disingenuous.

No, you are telling me, and many others in fact, what we were doing. And you're completely fucking wrong, which is rather the point of this entire discussion. Your biases lead you to believe these things, and the idea that what I am saying is true, doesn't fit in your head.

I showed you an example of a pain-free experience: "brew install stack && stack setup && stack build" just working. What was your pain-free experience, installing a package that had a multitude of dependencies?

Again, I can give you hundreds of different answers to this. Depending on the context. Suppose I did. Can we please then address the question?

The question is whether Stack contributes to a pain-free experience. I can show how it does (e.g: via showing simple commands to install Haskell software that Just Work, with very little effort on author side too). Can you do the same?

to put it in other words: to claim a tool is useless (are you not?), you have to show how it is inferior in every circumstance. it's enough that I show one circumstance where you can't (and I believe I have, not even a rare one) to disprove you.

By "show me", I mean, actually come and show me. I want to watch you provide some improvement that I simply cannot conceive of right now. I want to learn what it is that I am missing. I want to see it with my own eyes. Don't give me a shitty mac command that works, sometimes.