First steps into Scala

For over a full year now, I’ve been looking into Scala. I have heard many people talk about it passionately and it just got me interested. Also a lot of big companies are investing in this new language. I just figured I had to check it out.
In my 4 years of Java programming, I’ve learned the Java EE stack, (Spring and Java EE) and I must say, not much has changed since then. We got the long awaited release of Java 7 (with lots of features missing) and in 2009 Sun released Java EE 6.
Java EE 6 was a cool release and I have blogged about it for a few times but it is not more than just more abstraction of the same concepts. Spring hasn’t really been moving forward at all. When you look at the release which was used when I started programming professionally and the one we use in production, it is largely still the same version. There is a 3.0 release but to be honest, it is not very compelling.
So after hearing people like Dick Wall talk about Scala for a long time, I decided to pick it up. The first thing I have tried was the Scala Koans.
Scala cones is a project on github that helps you to learn a language by correcting failing tests. At the time the Scala Koans project was still in the very early stage and I did not get them to work and gave up rather quickly.
My second attempt at Scala was when I had some spare time and I wrote a simple application which parsed some XML. This worked but in the end this only took me 5 minutes, looking back at it now, I did not use any language feature that was an added value. The only thing I did, was write Java in Scala.
In the mean time I joined the Belgian Scala Enthousiasts and I’m following the mailing list, but still, I couldn’t really write a true Scala application. I didn’t even get the feeling I was hitting it off.
At Devoxx 2011 I was determined to go and see the Scala talks and things that have to do with Scala. I ended up seeing 2 talks about the Play! framework, 3 talks about Scala and a talk about Akka. I did also talk to the guy’s at MongoDB and Typesafe.
Devoxx 2011 was a real eye opener for me to get started with Scala. There were many reasons, first of all there were the talks.

The talk about play! 2.0 showed me how to build a web application with Scala. It also demonstrated what a cool framework Play! is.
The Akka talk showed me how to create super scalable and decoupled applications. It is written in Scala and integrated with the play! framework (version2.0) which was a plus for me.

The talk from Matt Raible didn’t really show me something technical. His talk was about some technologies he wanted to learn (Scala, Play, Coffeescript, {Less}, scalate and jade). He wanted to talk on Devoxx so badly so he just submitted a talk. At the time when he submitted the talk he didn’t know any of the technologies he was going to talk about. He even waited to start learning them until his talk got accepted. Only after the approval, he started learning and blogging about these technologies and then showed what he built at Devoxx. His talk was about the same thing which I was trying to do for over a year, but never pushed through. It might sound corny, but this talk was the real boost for what I’m doing now.

On the other hand I had 2 interesting chats in the downstairs hall.

One was with a mongoDB guy. He showed me the API he had built for connecting with mongoDB from Scala. Unfortunately, I did not get his name… The other was with Henrik Engström, a developer who works at Typesafe (A company founded by Martin Odersky, the creator of the Scala language and next to Scala they also house the play! framework and akka).

We just talked about how you can use scala in web applications.

When I got back from Devoxx, I literally got home and downloaded the Scala runtime, the Typesafe stack (at the time this was only Scala, Akka and the Scala IDE) and the beta of the Play! framework. I have a small project in my head that I’ve been thinking about for some time now and I started implementing it.

Based upon the 3 Scala examples with which the Play! 2.0 beta ships, I’m learning the language bit by bit. But there were a lot of language features I didn’t really grasp. I tried to look into the scala doc but got even more confused. I knew that Typesafe is offering a free book ‘Scala for the Impatient‘, so I decided to check it out. I downloaded that book and started reading it. Things cleared up immensely. I now understand why people say Scala isn’t complex, it just looks that way. Well it’s true. It also explains the weird things you see in the Scala API documentation.
Now I’m working with Play! 2.0 and Scala. When I’m getting the hang of it, I’ll also try integrating Akka and probably deploy it on Heroku and see what it can do.
I’m going to try to keep documenting my steps into Scala, Play! and Akka. I’ll see where It takes me.

Devoxx 2011: A crash course in Scala

Devoxx time again, 4th year that I’m attending. This morning I went to see the talk by Mario Fusco and Kevin Wright. The first part was by Mario and handled the Scala basics. The talk itself was a bit messy. It was a mix of API features and a comparison with Java, Groovy and Haskell.
He showed some cool language features, but overall it was just an API features list, but the demo that was given was pretty cool. The demo showed how easily you could create a DSL with Scala.
In 2 minutes he was able to write something like this.

   3 times{

Eventually the code printed “hello” 6 times. It is a bit a trivial example, but really fun to see what the power is of scala.

The second part of the talk was about how Scala would be agile in a project. Kevin also emphasized on the way we can write code that is very readable for developers and for the business users. He started with an example that he apparently stole from Dick Wall :-). The example just showed how everything in Scala is manipulable.

A long time ago in a galaxy far far away

translated into


So these are just a class (A), a few methods (long, ago, a, far and away) and some vals (time, in, galaxy and again far).
This was quite nice and showed the potential to build readable code for the business users.
For a more powerful example he referenced to a gist he created on github, where a string of validation rules can easily be added to a processor and then return the result. (on top you have the method declarations, on line 44 you got the actual processor that is being defined and at the bottom you find some test with the result in comment).
Again, I heard that the best way to start with Scala is to write your tests in Scala. This code does not go into production so it does not create a risk, but the developers start playing with and learning Scala so they get a good feel about what is possible.
The most important thing I remember from this talk is that you can learn a fair amount of Scala in 2 weeks, but you’ll need more time to learn a specific business domain. By writing your business apps in readable Scala, you could lower the step to get into the business.
It was an interesting talk that showed possible usages of Scala in a real environment, but I’m not sure it convinced many people to start using Scala.