nullability is directly related to the value classes effort (the top article mentions value classes, and the JEP you linked mentions nullability): in order to get the most benefit out of value classes, you need some way to express guaranteed non-nullability to avoid needing to encode null (imagine Point[] vs Point![]): https://cr.openjdk.org/~jrose/values/flattened-values.html#i...
'Value' classes would be useful in arrays only + some version of direct buffer mapping. All other cases are pretty uninteresting when it comes to performance or memory layouts.
> For all the reasons listed above, it's probably impossible to narrow in on one date and say with any certainty that this is when the game was released. But if we need to celebrate somewhere in the neighborhood of late January, then the last Sunday of the month (this year, the 26th) seems like the best candidate.
The post seems to suggest that it be a "floating" day of celebration rather than "fixed" on January 26th of every year.
> Java even plans to remove them from the language
The "Alternative techniques" section of the JEP suggests to use Cleaner.register, which was created as a replacement and has a similar API to Go's runtime.SetFinalizer.
