News for hackers. Stuff that matters.
Re:Thinking in Types by bilalq on Friday May 02, 2014 @01:42PM (#7687050)
The ecosystem plays a big part in this. NPM is actually a pretty nice package manager to work with. Cabal, on the other hand, took me quite some time to setup and use.
Re:Thinking in Types by tel on Friday May 02, 2014 @01:53PM (#7687094)
Cabal is actually an extremely nice package manager... it just, like much of Haskell, likes to tell you things won't work far before they fail. In particular, building things with Cabal requires that everything compiles together successfully. This is a much stronger requirement than NPM and has push some more sophistication into the dependency resolution Cabal does.
Re:Thinking in Types by freyrs3 on Friday May 02, 2014 @03:19PM (#7687576)
Indeed, if we deferred all type errors and compile failures from Cabal to runtime like Javascript/NPM then nobody would complain about Cabal! I think it's unfortunate that Cabal get's so much unnecessary blame when the problem is often in some other place entirely.
Re:Thinking in Types by dllthomas on Friday May 02, 2014 @06:20PM (#7688516)
This is mostly true, but I think we do see more dependency related issues than other languages. My working theory is that this is because we wind up building more small, generally useful packages that get used by lots of things and which can therefore be in conflict. I haven't set out to carefully validate this, though.