Why does Mendix use empty instead of null?

Don’t know if it was asked before, but I’d like to know the reasoning behind Mendix using ‘empty’ instead of ‘null’. It’s very hard to explain to people the difference that your check on ‘empty’ does not check on an ‘empty string’, but whether it’s defined/initialized or not. Java itself uses ‘null’ to define a value that’s not defined and has functions on string called .isEmpty() to check for a zero length string (not ‘Mendix’ empty/null). So in Java you have: Java: $string == null → Mendix: $string = empty Java: $string.isEmpty() → Mendix: $string != ‘’ Just never made sense to me why it was called empty, while it means something else than empty.
1 answers

I suppose you cannot compare Java with Mendix. Mendix is a platform which generates Java code under the hood. Java itself is a programming language.

Mendix code has its own syntax, Java has also its own syntax. It is just what you agree on.