News for hackers. Stuff that matters.
Re:Why the world needs Haskell by laureny on Wednesday July 10, 2013 @02:40AM (#6017853)
> Otherwise, when your program throws a NullPointerException you'll have no way to know where that null originated from.

Actually, it's the other way around: NullPointerExceptions are typically trivial to track down.

Finding out at what part of a monadic computation the return of a function put a None when there should have been a Some is much more tricky.

Re:Why the world needs Haskell by chongli on Wednesday July 10, 2013 @11:56PM (#6024403)
Finding out at what part of a monadic computation the return of a function put a None when there should have been a Some is much more tricky.

This is where Either comes in handy. Either allows you to attach extra information to the error condition (such as a String). This lets you have the same properties of Maybe but with more information when you need to disambiguate.

Re:Why the world needs Haskell by tome on Wednesday July 10, 2013 @04:47AM (#6018184)
> Finding out at what part of a monadic computation the return of a function put a None when there should have been a Some is much more tricky.

The point is you don't have to, because you don't use Maybe where you know statically that there can't be Nothing!

Re:Why the world needs Haskell by laureny on Wednesday July 10, 2013 @12:12PM (#6020724)
That's the theory. In practice, your code is clearer if you use Maybe's all along the composition path, otherwise you spend your time unboxing/lifting values.
Re:Why the world needs Haskell by aninhumer on Wednesday July 10, 2013 @01:56PM (#6021605)

    let x = y
is not a lot more complicated than

    x <- y
Re:Why the world needs Haskell by tome on Thursday July 11, 2013 @06:08AM (#6025246)
No you don't.

    clearCode = funcWithMaybe <=< (return . somePureStuff) <=< anotherFuncWithMaybe