I work with a lot of Haskell beginners and the Cabal problems went away when sandboxes were added to Cabal and the learners started using a sandbox for every project.

I've only seen a handful (one hand, 5 fingers) of problems since then that weren't attributable to, "wasn't using a sandbox". Of those, about half were the user doing something uncommon/unusual.

I have a tutorial here http://howistart.org/posts/haskell/1 which among other things, covers the basics of using sandboxes.

Library maturity is my only worry with production Haskell. Not enough eyeballs and all that. It's not enough to stop me or my colleagues using it in production though. I can fix libraries, I can't fix Scala.

On Fri, Apr 17, 2015 at 1:21 PM, Joe Hillenbrand <joehillen@gmail.com> wrote:

> On Fri, Apr 17, 2015 at 6:21 AM, Gregory Guthrie <guthrie@mum.edu> wrote:
>
> And in my experience the cabal problems are the "fatal-flaw";

Big +1 here. Cabal is the biggest thing keeping me from aggressively
promoting Haskell in industry. The risk of promoting Haskell now is
that people will try out Haskell, hit a cabal issue, give up, and then
form a bad opinion of Haskell because of it.

There is saying "If a user has a bad experience, that's a bug."

I've been patiently awaiting the Backpack overhaul before promoting
Haskell in the workplace. [1]

[1] https://ghc.haskell.org/trac/ghc/wiki/Backpack

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe