I have been playing around abit on scala, and I have probably drawn a conclusion for it now.
Not yet.
What I essentially mean is that I am not really to invest time and effort on it.
Primary reason? The tools just don’t cut it yet.
I tried out Scala on Eclipse first. The experience was pleasant. But getting the JUnit integration to work on it was a pain. Massive pain. But then I tried to live without it.
And then I tried it out as a Maven project. Not as a normal, ordinary one, but a Maven Multi-Modules project.
It almost worked, but I had to build and install each Maven modules for my Scala project, so that their dependencies can be resolved. And once I resolve this, somewhere the editor keep complaining about missing function definitions in the code. The functions were imported from a dependency library. The JUnit tests run fine via Maven.
And then I heard that Netbeans had better JUnit integration. And I had higher hopes that the Multi-Modules project were better in Netbeans.
Well the JUnit tests sorta work. But they don’t link back to the line causing the error properly. The dependencies seem to be working if I recall correctly. But the editor still complains.
And so I gave up.
Don’t mistake me. I will still agree that Scala is a rather interesting language (and in many ways better than Java). Functions are first class citizens, closure support. Traits (though I did not test if they work fine across Maven Multi-Modules). I did wish they have named parameters support, so that my code will read better. But without the minimal tool support I probably will not make the leap on it. All I need is better integration with Unit Testing on my IDE, Maven multi-modules support, and proper error checking. :(
Posts
