Over a million developers have joined DZone.

Only One Language Solves the Whole Problem: Scala

DZone's Guide to

Only One Language Solves the Whole Problem: Scala

· Java Zone ·
Free Resource

Learn how to stop testing everything every sprint and only test the code you’ve changed. Brought to you by Parasoft.

I'm writing this post from the Groovy/Grails eXperience, awaiting the start of registration and the actual first sessions. It's a bit ironic that at this time I have to come to this conclusion: Scala is the only language that solves the whole problem.

So what's the "whole problem" then? It's programming for multi-core processors. And static typing. Throw away your Python, Ruby and Groovy books. The dynamic language skills you've learned may still be useful in other settings, who knows. But if dynamic languages are your thing you're on the wrong side of the aisle.

It's Scala! Think about it. You can write your own web server in Scala - after all Tomcat is written in Java. Scala is somewhat readable, but if you know ML you'll feel right at home. As you all know using multi-core processors efficiently is the future. Intel has an 80-core processor! Think! It's Scala all the way.

Java is old and needs replacement anyway. People get excited about dynamic language but they're wrong. Dynamic languages are useless! Useless! You can't even refactor! What's that about?

Anyway, I'm gonna enjoy this conference, do my sessions and on the plane home start to learn Scala. I want to secure my future man!

Happy coding!

Get the top tips for Java developers and best practices to overcome common challenges. Brought to you by Parasoft.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}