The biggest reason why is because the Java team works as hard as possible to get as much user feedback before putting a feature out there. Part of that means t

The biggest reason why is because the Java team works as hard as possible to get as much user feedback before putting a feature out there. Part of that means that they will release minimal versions of a feature (records), and then observe how people use them before they start adding the "obvious" Quality-of-Life changes. It's painful for those of us who are here when these features are just now releasing. But the end result is a feature that has less chance of screwing over other potential features. It's best to think of it as a short term cost for a much longer term gain. Moving slow like this means that they will release a feature that is more cohesive than it otherwise could be.