News for hackers. Stuff that matters.
Re:Typesafe raises $14M to commercialize Scala by seanmcdirmid on Wednesday August 22, 2012 @09:58AM (#4417341)
Static (and even dynamic) type safety is always a shade of gray vs. a black and white thing. A language that is 100% type safe is a language that doesn't do very much (...or requires a theorem prover). Scala is very pragmatic in that regard.
Re:Typesafe raises $14M to commercialize Scala by typetheoristic on Wednesday August 22, 2012 @11:39AM (#4417880)
I'm not sure what world you're living in, but Haskell and ML seem to offer some measure of type safety and are also quite practical. Sure there is unsafePerformIO. But the problem is with Scala you don't even need to use unsafe language features to get an unexpected class cast exception. Given that you worked on Scala I'm rather surprised you don't know about this already.
Re:Typesafe raises $14M to commercialize Scala by seanmcdirmid on Wednesday August 22, 2012 @12:10PM (#4418074)
Could you be more specific? Is the compiler promising more than it can deliver, or are you saying the compiler could check something but simply doesn't?

You can have 100% type safety in a straight jacket, but scala pushes what it tries to type check to an extreme limit; "safe" but then also not as conservative as Haskell or ML. I see scala as the c++ of statically typed languages, filling that niche where you need more from your managed language and are willing to take a leap, but this is controversial and a personal opinion.

Re:Typesafe raises $14M to commercialize Scala by SourPatch on Wednesday August 22, 2012 @02:14PM (#4418740)
Do you have an example of code that will throw an unexpected ClassCastException?
Re:Typesafe raises $14M to commercialize Scala by pkolaczk on Thursday August 23, 2012 @04:32AM (#4421438)
I never, ever had a ClassCastException in Scala that I wasn't warned about by the compiler. Maybe in theory you are right. But what counts is practice.