“This was backed up for me by a talk by Paul Phillips, a major contributor to the Scala compiler”
Full comment
I took Odersky's online course and used it for one project. It runs my home lighting system. My experience was definitely mixed. I liked the language for its ambition. I think the notion that OO and functional approaches are complementary worked very well for me. There were a lot of interesting ideas in the language and the ecosystem. However, there were a number of downsides. I came across a couple of bugs that were well known and apparently people were just expected to work around them. As others have said, compile times were terrible, and the tooling wasn't great. And at a one day Scala unconference one of the prominent Scala community members was a flaming asshole to me, which definitely didn't help. What really put me off, though, was what Bruce Eckels described: "I’ve come to view Scala as a landscape of cliffs – you can start feeling pretty comfortable with the language and think that you have a reasonable grasp of it, then suddenly fall off a cliff that makes you realize that no, you still don’t get it." link This was backed up for me by a talk by Paul Phillips, a major contributor to the Scala compiler: this video So in the end, I'm likely to look elsewhere. The next language I'm trying out is Kotlin: link It's from the IntelliJ IDEA people, who I trust a great deal, and I just got done working through their nice in-browser IDE tutorial: link So far it seems to have all of the things I like about Scala plus a number of improvements. E.g., fast compile times were a