4 ms·

Sure this post is probably not for me, but as to feedback, i will start that page with a paragraph or sentence or two of what Jakarta is ?? Something something

Sure this post is probably not for me, but as to feedback, i will start that page with a paragraph or sentence or two of what Jakarta is ?? Something something java ?

bee_rider 4y ago
I disagree. A "what's new in <X>" post shouldn't describe what <X> is. Most of the people interested in updates on <X> will already know what it is, so adding that information to every article would be redundant. They helpfully link to the jakarta.ee site which has an about page.
exabrial 4y ago
Jakarta EE is all of the Java EE spec that are now open sourced. Right now in Java-land, the big development ecosystems are Quarkus, Spring Framework, and Jakarata EE. Jakarta EE's big advantage is CDI, which is a very nice dependency injection container and allows applications to be broken down and composed into easily testable modules. Quarkus partially implements CDI and has its own set of APIs. Spring has their own DI container that is showing it's age, but is still quite popular.
- zokier 4y ago
  Quarkus is "just" a Microprofile implementation. And Microprofile is largely evolution of JavaEE. Spring might have been a breath of fresh air in the JavaEE 6-7 days but I feel it has been since been leapfrogged by JavaEE/MP
- gavinray 4y ago
  Quarkus is Jakarta EE compatible (MicroProfile), for the subset of Java/Jakarta EE that it implements. That's largely the appeal. The most recent release of JEE has a new "Core" profile, which is stripped down to bare minimum for AoT-compilation and small memory footprint and implements CDI 4.0 Lite (based on Quarkus' "ARC" implementation) https://jakarta.ee/specifications/coreprofile/10/ https://jakarta.ee/specifications/coreprofile/10/
throw_m239339 4y ago
Java EE is basically a collection of API that are shared accross different Java web servers. It's a spec so basically you develop your java app on say glassfish server and you can deploy it on websphere, the servers holds all the libraries you need to run your app, so you can just deploy some small java zip file. Because of trademark issues with Oracle around the name Java, the open source community had to rename all its API jakarta instead of java which is completely stupid and is a demonstration that Oracle is just here to milk the name Java.
- pantulis 4y ago
  Would it be more correct to say "Java application servers" instead of "Java web servers"?
- deleted 4y ago
  [deleted]
whartung 4y ago
Oracle open sourced and released the bulk of the Java Enterprise Edition specifications and source code. But what they did not do, is release the Java trademark. So, the whole kit had to be called something else (in this case they chose Jakarta, which has history in the Java community and lets the colloquial "JEE" still work). Part of this process what they had to rename ALL of the Java EE packages from the original "javax" root name to something else, again, in this case, "jakarta". This has been a several year process that's held up a lot of advancement in the platform as it transitioned out of Oracle and over the Eclipse foundation. At this point with moving to Java 11 and supporting Java 17 (no small feat), and having all of the packages renamed, repackaged, re-released, Jakarata EE is probably "finally free" from where it was back in "Java EE 8".

Sure this post is probably not for me, but as to feedback, i will start that page with a paragraph or sentence or two of what Jakarta is ?? Something something java ?

bee_rider 4y ago

I disagree. A "what's new in <X>" post shouldn't describe what <X> is. Most of the people interested in updates on <X> will already know what it is, so adding that information to every article would be redundant. They helpfully link to the jakarta.ee site which has an about page.

exabrial 4y ago

Jakarta EE is all of the Java EE spec that are now open sourced. Right now in Java-land, the big development ecosystems are Quarkus, Spring Framework, and Jakarata EE. Jakarta EE's big advantage is CDI, which is a very nice dependency injection container and allows applications to be broken down and composed into easily testable modules. Quarkus partially implements CDI and has its own set of APIs. Spring has their own DI container that is showing it's age, but is still quite popular.

zokier 4y ago
Quarkus is "just" a Microprofile implementation. And Microprofile is largely evolution of JavaEE. Spring might have been a breath of fresh air in the JavaEE 6-7 days but I feel it has been since been leapfrogged by JavaEE/MP
gavinray 4y ago
Quarkus is Jakarta EE compatible (MicroProfile), for the subset of Java/Jakarta EE that it implements. That's largely the appeal. The most recent release of JEE has a new "Core" profile, which is stripped down to bare minimum for AoT-compilation and small memory footprint and implements CDI 4.0 Lite (based on Quarkus' "ARC" implementation) https://jakarta.ee/specifications/coreprofile/10/ https://jakarta.ee/specifications/coreprofile/10/

throw_m239339 4y ago

Java EE is basically a collection of API that are shared accross different Java web servers. It's a spec so basically you develop your java app on say glassfish server and you can deploy it on websphere, the servers holds all the libraries you need to run your app, so you can just deploy some small java zip file. Because of trademark issues with Oracle around the name Java, the open source community had to rename all its API jakarta instead of java which is completely stupid and is a demonstration that Oracle is just here to milk the name Java.

pantulis 4y ago
Would it be more correct to say "Java application servers" instead of "Java web servers"?
deleted 4y ago
[deleted]

whartung 4y ago

Oracle open sourced and released the bulk of the Java Enterprise Edition specifications and source code. But what they did not do, is release the Java trademark. So, the whole kit had to be called something else (in this case they chose Jakarta, which has history in the Java community and lets the colloquial "JEE" still work). Part of this process what they had to rename ALL of the Java EE packages from the original "javax" root name to something else, again, in this case, "jakarta". This has been a several year process that's held up a lot of advancement in the platform as it transitioned out of Oracle and over the Eclipse foundation. At this point with moving to Java 11 and supporting Java 17 (no small feat), and having all of the packages renamed, repackaged, re-released, Jakarata EE is probably "finally free" from where it was back in "Java EE 8".