It really depends on what you are looking to teach!
For professional dev with lots of packages and different projects then sandboxing is a must.
I imagine for a lab you could get away with what's in the haskell platform. I got cabal-dev going on a windows box not too long ago. When I get home I will have a tinker.
I am sure someone with more windows experience than I can chime in.
Thanks for the clarification and info.
>From this I then deduce:
Using "cabal install" is dangerous, and leads to broken package structure (inconsistent package versions and shadowing).
Better to use cabal-dev,
But it requires network, which is external to Haskell, and a pain to build (on windows)...
Thus, no good solution on Windows - is this right?
Since Windows is 94%+ of computing environments today (all of our labs use Windows, and "standard" IDEs), then Haskell is not a good fit?
We want to use Windows since that is what students will generally see in their professional environments.
I hope not...!! :-)
-------------------------------------------------------
>> Ahh, I think network is a pain to build on Windows.
>> I don't as a rule do any haskell on windows because of the headaches of msys / mingw.