Apache Groovy used to have the === operator in its earliest versions, but dropped it in favor of using a custom .is() method. The meaning of == is different to its use in Java, catching out many -- "happy" is not the word I'd use.
Same here. Groovy rocks my world and is the main reason I've barely even looked at Java 8.
If Groovy rocks your world, wait until you meet Kotlin...
If Kotlin rocks your world, wait until you meet the Scala.
I met Scala a few years ago, we had some fun together but she's way too high maintenance.
Apache Groovy has some long-standing governance issues, e.g. the groovy-lang.org DNS is owned by a single individual. Other languages such as Kotlin and Scala have more, er, responsible governance.