Tony Morris

Scala developers from Java should know about the problems of "Y throws X" vs "Either[X, Y]" - having effects as types works much better!

@puffnfresh why doesn’t Scala make them the same?

@natpryce Scala doesn't have checked exceptions (or any effect system, in fact).

@puffnfresh … could the compiler have made JVM exceptions appear to be Either’s instead of making the translation the programmer’s job

@natpryce @puffnfresh Possibly could now, Either came relatively recently to Scala.

@tomjadams @natpryce @puffnfresh that's the purpose of Try, which is analogous to either with Throwable on the left and some catching kit

@jedws @tomjadams @natpryce @puffnfresh Try is a bit silly, imho. Scala just needed a right biased either like https://github.com/scalaz/scalaz/blob/scalaz-seven/core/src/main/scala/scalaz/Either.scala#L395 …

@benkolera @tomjadams @natpryce @puffnfresh agreed, we don't use it, but it is in there for the purpose and is used for instance by Future