Is Groovy's assert a good idea for production code, unlike Java's assert?

Question

In Java it\'s known that using the assert keyword is usually a bad idea, as its behavior is dependant on the runtime enviornment (it doesn\'t do anything by def

Answer 1

Groovy assert is always executed in production code, and I recommended to use in production. I see the following as being roughly equivalent, but the Groovy version is more compact

Groovy

assert file.exists(), "$file does not exist"

Java

if (!file.exists()) {
    throw new SomeRuntimeException(file + " does not exist");
}