Scala and Java

When you say Ruby, you say Rails. When you say Groovy, you say unit-tests, scripting and integration. Well that might be over-acted, but that’s what most people make of it.
Some people remark Scala is best-suited for backend-code, or very good at parallel code, but apart from that I’ve never heard that Scala is the language for the Lift framework. Or the language to use when you want to create multi-threaded code. What I hear mostly, Scala is the new Java.
Would that be true: could you use Scala as a dropin replacement for Java, as, let’s say, a Java 2.0 or Java 8?

In the coming postings I want to investigate that claim using my knowledge of experience in Java/J2EE and my complete lack of experience in Scala. Can you say to you’re developers, or yourself, from this day on, we’ll use Scala instead of Java to do our development?

For now, I found this nice presentation I want to share: Introduction To Scala For Java Developers by Miles Sabin.

2 Replies to “Scala and Java”

  1. I can say it, as it’s what we are doing since december 2009. We started to use Scala along with Java, and soon get bored to switch back to Java bloat, and we dismissed it completely.

    So now, we are three developers in a young company that are building a product in Scala – but of course, we are heavily making use of the gazillion good Java libraries available around there.

    I can tell that just having a language that is always standing up between what you want to do and what it allows to do (as was Java for me – I like generics, or I would really have been able to like them) is a big win.

    But really… it’s more a matching between you wit and the language than what others are saying that is important to have the work be done…

  2. Hello Francois, thanks for your comment! Very interesting , and I like your blog.