Hacker News new | ask | show | jobs
by imtringued 539 days ago
It would have been trivial for record types to be non-nullable by default.

Record types are 3 years old and they are already obsolete with regards to compile time null checking. This is a big problem in Java. A lot of new features have become legacy code and are now preventing future features to be included out of the box.

This is why the incremental approach to language updates doesn't work. You can't change the foundation and the foundation grows with every release.

I am awaiting the day Oracle releases class2 and record2 keywords for Java with sane defaults.