* important concepts such as f-bounded polymorphism, covariance, contravariance, implicit parameters and methods, etc.
* traits that solve the diamond problem with multiple inheritance
* functional programming concepts including monads
* advanced concurrency concepts via the actors library
* pattern matching via case classes and extractors
* that type inference can make you highly productive in a statically typed language
Could you state the case for scala, in terms that someone not familiar with it, could appreciate?
Oh really? Type declarations and the like are at most 10% of code. That means that eliminating the need to type them, which is what type inference does, can't decrease code size by more than 10%. It's unlikely that that 10% takes more than 10-15% of development time.
The fact that those are important concepts in Scala doesn't make them important concepts.
> traits that solve the diamond problem with multiple inheritance
There are lots of solutions to the diamond problem. The fact that scala uses traits doesn't make traits important.
> * pattern matching via case classes and extractors
Again, so what?
Scala is full of elegant mechanisms to solve problems that resulted from design choices. The elegance of those mechanisms or their importance to scala doesn't make them important. After all, one might reasonably have made different design decisions, making them irrelevant.
The claim was that scala is special. However, the argument doesn't support that claim. It's a list of "me-toos" and hyperbole.
For example, every language with multiple inheritance has some mechanism to deal with diamonds. Type inference is useful/interesting, but it doesn't result in "highly productive".