Tony Morris

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 prefer Nix for professional Haskell work, even though curation of packages is not perfect. If we're going to say Stack is a mistake for teaching Haskell, I'd really like to know exactly what bad happens to the student.

Stack was such a massive improvement over what came before. If it's a mistake for teaching, that's a very recent fact.

I have respect for @dibblego. I've come around to his position many times in the past. So it's totally frustrating when he goes off on these anti-Stack bends and I just can't track the argument.

I share your opinion exactly.

No argument was made. Also, you're wrong. It's not recent. It's an opinion shared by many; in particular, those who are committed to teaching effectively.

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.