It is being touted as a serious win for Scala that it integrates so smoothly with Java. This claim looks good on paper until you realize that almost every Java developer uses an IDE. Wait, though... doesn't Scala have good plug-ins for Eclipse, IntelliJ IDEA, and NetBeans?
Thus far these plug-ins are a good proof of concept, but they are all far from being ready causes to replace Java in a professional workplace. The IntelliJ IDEA plug-in is the best of the lot from my initial impression. I regret that the Eclipse plug-in is the weakest since Eclipse is my Java IDE of choice. All seemlingly have trouble when you try to use Scala from Java. Again the IntelliJ plug-in makes the best showing in this area.
Frustratingly, none of the plug-ins let you write Scala scripts in the IDE. They just scream errors at you if you try. This seriously hampers the use of a very convenient aspect of the Scala language. In retrospect this is probably the best entry-point for Scala into an existing project and the door is held firmly shut by narrow plug-in designs.
Reading through Programming Scala from the Pragmatic Bookshelf I found myself often impressed by the removal of obvious gaffes in Java abstractions. However, I see now that these abstractions offer little for how much they distract the actual process of simply getting things done. No more distracting than Java, but without equivalent tool support I won't be switching.
I was hoping Scala would bring more to the plate. Unfortunately, I am left with a sad conclusion I made after diving deeply into Ruby and then Groovy programming and coming out sorely disappointed. At that time I concluded that clever abstractions don't encourage team productivity, but rather impede it by encouraging flights of fanciful cleverness and wildly varying coding styles.