On 4/16/23 8:47 AM, Glavo wrote:
I understand that Java 21 is around the corner and you have a lot of work to do, so I'm sorry for taking up so much of your time. But for this issue, I think it really needs to be corrected. If new APIs cannot be added in Java 21, it means that correcting these legacy issues in the community will take at least two more years. I earnestly request that you pay more attention to this issue, and I am extremely grateful.
There is a lot more to say about the technical issues, but I want to highlight the above. It indicates that you are trying to rush this change into JDK 21 because otherwise the solution will take two more years. This is a mistake. This is why we moved the JDK to six-month releases. Yes, I'm aware that JDK 21 is an Oracle LTS release. Rushing something into the next release because it's an LTS is a *bigger mistake.*
The reason that it's a mistake is that if you rush something in, and errors are discovered later, *other people will have to maintain it in perpetuity.*
Again, there are many other issues to discuss about this change, and in fact there are legitimate problems in this area that ought to be solved. However, I refuse to discuss them if it contributes to an immature change being rushed into JDK 21.
s'marks
