![]()
Hi Ryan:
I'm part of the guardians group as well and very much support the joint statement.
I'm of the opinion that some efforts -- standing apart from Java EE -- got underway (and rightfully so) and then also gained traction/mind-share (and rightfully so) do to the pace of Java EE releases which at time seemed glacial.
I really am hoping for a few big positives to come out of the new Jakarta EE governance process. These things (and some wishes) include:
- The release cycle becomes much faster
- Perhaps even quarterly like the cadence over at WildFly
- Stays in line with OpenJDK
- Performance metrics are published with each release so we stop comparing "today's apples" with "apples from 4 or 5 years" ago
- X is to slow versus something else
- Y is to heavy versus something else
- Metrics as part of the Jakarta TCK maybe?
- X implementation is more performant than Y implementation on a fair bench test
- Performance unit tests in the TCK??
- The community of different projects trust the governance at Eclipse and rally around Jakarta EE
- Heavy cross pollination into/out of Jakarta EE
- Ideally as many projects as is possible fold into or find a common ground/base in the Jakarta EE Standard
- These other projects have many cool and innovative ideas
- Instead of spinning out into another project they are used to drive the Jakarta EE Standard
- A Cornucopia of Profiles and Blueprints if you will
- Different Approaches and Projects become TRUE profiles/blueprints easily cherry picked/selected/configured by developers off a main server core
- e.g "MicroProfile" really as a Jakarta EE "Profile" but also part of the Jakarta EE core capabilities
- e.g. Spring Boot (and similar projects with "mind-share") are encouraged to return Jakarta EE fold
- Bring their innovations with them
- Become a blueprint or profile
- Not Invented Here (NIH) is a short sighted view
- No more "us vs them" thinking with regard to the ecosystem
- More "us and us" and we all have cool things to share thinking
- The TCK expanded if necessary to ensure all projects interface well
- Even if the profile or blueprint is aimed at a specific problem domain (as much as possible)
- Again trust engendered by the Eclipse foundation bringing the many sub-groups that depend upon and sprout in and around the Java/Jakarta core together
- The ecosystem as a whole is more important than any particular organization or project
- Advocacy groups like Java EE Guardians ensured a voice at Eclipse.
All my $0.02 but boy these are EXCITING TIMES. Everyone in. Let's have fun.
Let's all do what we can to move Jakarta EE at Eclipse forward.
Dennis
