I shouldn't have said "crippled." It's just much more limited than when used in Erlang.
From digging a bit it appears to be somewhat the JVM's fault[0] and quite a lot of it is simply that it's a different type of language from Erlang.
In Erlang, nearly every line of code involves pattern matching, regardless of whether the developer takes advantage of it or not. Every assignment statement, every function return, every function parameter, is an exercise in pattern matching. It's at the core of the language, not an add-on.
As I mentioned in another comment, a closely-related feature that really shows it to its full advantage is multiple function heads/clauses.
OK, I also don't like Scala's inability to deconstruct in the parameter list. I come from an ML background where that is possible. But I found it less bothersome in practise than I had originally anticipated.
Erlang has pattern matching on bits [1] which is convenient, that would be nice to have, especially when writing networking software.
[1] P. Gustafsson, K. Sagonas, Efficient manipulation of binary data using pattern matching.
From digging a bit it appears to be somewhat the JVM's fault[0] and quite a lot of it is simply that it's a different type of language from Erlang.
In Erlang, nearly every line of code involves pattern matching, regardless of whether the developer takes advantage of it or not. Every assignment statement, every function return, every function parameter, is an exercise in pattern matching. It's at the core of the language, not an add-on.
As I mentioned in another comment, a closely-related feature that really shows it to its full advantage is multiple function heads/clauses.
[0]: https://www.scala-lang.org/old/node/11982