+1 Erik and quote you:
I think that not providing technologies that were available in Java EE 8 (even if they came from Java SE) is very risky for the future of the project because it runs contrary to the expectations of backwards compatibility that might exist. In my opinion, backwards compatibility is essential and in the special case of Jakarta EE it is not only about what's actually in the specs but also about the perception of changes by the community.
Stated on another thread [linked below] , it seems that the current work being done in Jakarta EE 9 release is not considering carefully the pros & cons. At this time, we don't have the actual data from users, as an ecosystem, to sustain current desires of what effectively cut or not. Being patient while doing the work now seems the wisest step forward instead of graving into a whole that cannot be fixed later, Trust is lost via small actions & rarely lost with just 1 action itself. I am wary of what currently is. I am considering not only the coders but the users as both are core and important for this project's success.
Current methods are pushing on the side of radical steps, that is a red flag in itself for users. Are we really choosing to become that ecosystem?
Erik, you are one great example of a Jakartee whose arguments are impossible to ignore.
-- The power-of-preparation, POP, from this community cannot be underestimated or deferred. We have now.
The project requires individuals whose arguments are hard to ignore or push around, those who makes us understand our weakness are the most valuable contributors. -- Nov 26th forum Community thread