|Re: [jakartaee-platform-dev] Java SE 8 or 11 for Jakarta EE 9?|
The most critical thing is honestly showing progress so that no one is worried this is a "dump and run" operation after Jakarta EE 8 is done being transferred (along the same lines that this isn't a half-hearted and underfunded effort).
Java SE 11 is not that big a deal. Look at the numbers here: https://www.jetbrains.com/research/devecosystem-2018/java/. A whopping 85% still uses Java SE 8 (for many good reasons). This is also the reality I see personally amongst folks using Java EE. In fact, the percentage there is probably even higher if people are being honest.
Adopting Java SE 11 is valuable in sending a clear signal that the platform is modern and keeps up with a fast moving industry that J2EE and Java EE were probably not facing. Beyond that important signal, we can do with Java SE 8 for now.
Principal Program Manager
Java on Azure
Please note that views here are my own as an individual community member and do not represent the views of my employer.
On 11/3/2019 9:29 PM, Kevin Sutter wrote:
Since we're trying to nail down the Jakarta EE 9 content before early December, I'm going to start a few separate threads to discuss the major topics.
Back to the top