In a number of sessions I have attended in Software Architect 2010, the speakers mentioned Scala many times, particularly stating that Java is limited and that Scala is great both, since it follows the Functional Programming paradigm (not like Java that’s only Object Oriented) and that it is really fast.
This morning in the Better Software‘s November edition, there’s a short introductory article on Scala by Daniel Wellman. It quickly presents Scala as “Better Java”, reducing the code sizes by a factor of two.
Scala has been created by Martin Odersky, previously he created Java 1.3 compiler and co-created the generics in Java. Hence Scala has an excellent compatibility with Java. The Scala compiler compiles Scala into byte codes that JVM can execute, making Scala code executable anywhere where there is a JVM.
Scala is utilized in many places already with the likes of Twitter and Foursquare, which gives a rise to the Scala community and demand more from the contributors.
The question is: even if one wants to use Scala, what’s the right way to start. The article by Daniel Wellman suggests to start writing Unit Tests for Java using Scala, and that’s perhaps the easiest and safest way to go. It is possible to write Scala Unit Tests in for Java code using JUnit or TestNG however writing the Tests in Scala syntax.
Sure, why not give it a try? Especially when we already have experience with groovy.