News for hackers. Stuff that matters.
Re:Announcing TypeScript 0.9.1 by pkinsky on Wednesday August 07, 2013 @10:02PM (#6176938)
Java is not a good example of a statically typed language. Null pointer exceptions just don't happen in idiomatic Scala. For example, let's say I have 3 functions a,b and c, each with signature Int => Option[Int]. Any one of these can return Some[Int] or None.

Options, like all collections, can be chained together as such:

   for {
      x <- a(1)
      y <- b(x)
      z <- c(y)
   } yield z
this expression is of type Option[Int], and will never throw a null pointer exception. (Futures can be chained together with identical syntax)
Re:Announcing TypeScript 0.9.1 by seanmcdirmid on Wednesday August 07, 2013 @11:10PM (#6177151)
> Null pointer exceptions just don't happen in idiomatic Scala.

But match exceptions do.

Anyways, if I had to choose between unsound static type checking and sound dynamic type checking, I would definitely choose the latter.

Re:Announcing TypeScript 0.9.1 by happy_dino on Thursday August 08, 2013 @08:46AM (#6178529)
> But match exceptions do.

I'd call that non-sense.