Its right, Scala code is much smaller.
But, as we can see, both Java and Scala are composed by a single block of conditionals, loops and IO, everything in one method.
What I worry about is that people move out from writing not good code in one language to writing not good code in another language. The Java solution is horrible and not even what a Java developer should write. Using nothing but java: https://gist.github.com/2007714
After 12 years of Java, one should not use those Java techniques, they are old. Some are even C techniques (declaring the variables ahead, without any need).
One could also make use of libraries to make the Java code easier to understand, such as any collections library.
And thats what I am afraid of. Writing code that is hard to understand in one language, migrating to another, and writing code that is still hard to understand.
Comparing two languages, without its environments, just does not make sense. Not in 2012. Not leaving behind several other facts, such as scala compilation time and feedback cycle and much more.
One definitely writes less code in Scala, as we can see in our current project (+1 year) but both in Java and in Scala, the code presented is not a good example.
It is not the number of characters that you type that makes your program great. It is the good practices used.