Java Object Identity Is a 30-Year Trap. JDK 28 Is Breaking It.
JEP 401 officially proposing Value Objects for JDK 28 isn’t just a performance upgrade; it’s a philosophical coup. For decades, Java developers have been forced to pay an identity tax on every object, even when they were just silent data carriers. Now, we have to unlearn our most deeply ingrained assumption: that every object needs a soul.