You can read a bit more about those scala features (in this case compared to java) in this other article: http://www.scala-academy.com/resources/java-vs-scala h

You can read a bit more about those scala features (in this case compared to java) in this other article: http://www.scala-academy.com/resources/java-vs-scala http://www.scala-academy.com/resources/java-vs-scala "Is that supposed to convince me to use this in the industry, and apply my time?" I say in the article: «- Does this mean that I should use Scala? Can you get a job you like programming Scala? If so, then: yes! (Otherwise, unless you're rich, you need to pay your bills...)» If don't think you can get a job programming Scala (because of where you live, or another reason) I explicitly say you shouldn't learn it! :) But the rate at which Scala jobs are becoming available is relevant: I don't care if there are 200 Java jobs near me, as long as there are 3 or 4 Scala ones. As long as I have a Scala job, I don't care if the other companies are programming something else. If you can't get a Scala job - again: it's probably best to not even to take the time to learn it.