Interesting. They killed Java EE and now they embrace Jakarta EE. It seems, that there is a big customer demand for it. But the WebLogic pricing is really keen. So they have hopefully some very useful and unique features to justify it.
Oracle plays important role in Jakarta EE. They didn't kill Java EE but rather donated it to the Open Source community. Could they do better job in maintaining Java EE? Sure, but bashing Oracle for "killing Java EE" seems really cheap.
Technically they killed it. Because they are the only one institution which could evolve Java EE further. And yes, i know, that they donated it to the EF. =)
I guess it depends on definition if "kill" :). Do you consider Jakarta EE as last stadium of death for Java EE? Honest question
(I'm involved in the Jakarta EE project from the community side and would like to hear honest opinion about Jakarta EE)
Jakarta EE 10 is a year and a half old, and 11 is supposed to be out Q1 this year (so any day now?) but oracle is targeting only 10 a year or almost two from now?
Well, a lot can change between now and when WLS 15.1.1 is ready to begin its development cycle. As the release co-coordinator for EE 11, I am hoping WLS has an appetite for skipping 10 and going straight to 11 (cue Spinal Tap reference). But we'll see. I can say that the product roadmap support for the jakarta namespace is a big deal. I'm happy with that.
Oracle fucked Java up and they’re trying to make up for it.
Java EE was usable at some point, I remember using JBoss+Java EE server over Tomcat+Spring.
But they haven’t even tried to keep up with Spring.
Spring is incredible and they’ve done amazing work to make Java good.
It will be not that easy to migrate from a Java EE server to Helidon. Because Helidon offers only a fraction of the functionality, a Java EE server has. Maybe it is possible if you put the lacking libraries into you artifact. But in this case, you will end up with a Pseudo-Java EE-Helidon-Franken-Server. And i do not believe, that this is a good idea.
I've used both WebLogic and WebSphere for around 2 years each as it happens, and both work well. Now that people are able to see not every nail needs a microservice/docker/kubernetes hammer; it's time to reconsider the powerhouses, IMHO.
I use both back in the day. Web logic did its job. It was adequate. Websphere, holy shit. Everyone feared touching that piece of garbage. And holy crap every page looked the same. Whoever designed that garbage was obviously color blind.
Weblogic was fine via Cli for me, the UI was slow AF. Websphere... I literally wanted to drive down to ibm and kill them after using it for a few days.
If you want to bring your WLS, tWAS, WebSphere, or JBoss EAP workloads to Azure, we have a home for you at [https://aka.ms/java/ee](https://aka.ms/java/ee) .
Looking forward to the support for Java 17+. We're running a big application on Weblogic and although we're in a migration process, it won't be done anytime soon.
That said, Oracle made a similar statement last year, claiming "CY2023". It's kinda disappointing.
[удалено]
April 1st 2010?
No thanks
Interesting. They killed Java EE and now they embrace Jakarta EE. It seems, that there is a big customer demand for it. But the WebLogic pricing is really keen. So they have hopefully some very useful and unique features to justify it.
Oracle plays important role in Jakarta EE. They didn't kill Java EE but rather donated it to the Open Source community. Could they do better job in maintaining Java EE? Sure, but bashing Oracle for "killing Java EE" seems really cheap.
Technically they killed it. Because they are the only one institution which could evolve Java EE further. And yes, i know, that they donated it to the EF. =)
I guess it depends on definition if "kill" :). Do you consider Jakarta EE as last stadium of death for Java EE? Honest question (I'm involved in the Jakarta EE project from the community side and would like to hear honest opinion about Jakarta EE)
Jakarta EE 10 is a year and a half old, and 11 is supposed to be out Q1 this year (so any day now?) but oracle is targeting only 10 a year or almost two from now?
We aim for June/July 2024 for 11. So definitely not Q1
Well, a lot can change between now and when WLS 15.1.1 is ready to begin its development cycle. As the release co-coordinator for EE 11, I am hoping WLS has an appetite for skipping 10 and going straight to 11 (cue Spinal Tap reference). But we'll see. I can say that the product roadmap support for the jakarta namespace is a big deal. I'm happy with that.
Shows 2022 on [this](https://jakarta.ee/release/) page, what are you referring to?
The title of this post
It was late, I misread what you were stating, thanks,
Necromancy...
Oracle fucked Java up and they’re trying to make up for it. Java EE was usable at some point, I remember using JBoss+Java EE server over Tomcat+Spring. But they haven’t even tried to keep up with Spring. Spring is incredible and they’ve done amazing work to make Java good.
Wouldn't it be better for Oracle (and all of us) to focus on Helidon and offer a migration path off of WebLogic?
It will be not that easy to migrate from a Java EE server to Helidon. Because Helidon offers only a fraction of the functionality, a Java EE server has. Maybe it is possible if you put the lacking libraries into you artifact. But in this case, you will end up with a Pseudo-Java EE-Helidon-Franken-Server. And i do not believe, that this is a good idea.
I would imagine they are, but they will have plenty of customers unwilling or unable to modernize their apps
I've used both WebLogic and WebSphere for around 2 years each as it happens, and both work well. Now that people are able to see not every nail needs a microservice/docker/kubernetes hammer; it's time to reconsider the powerhouses, IMHO.
I use both back in the day. Web logic did its job. It was adequate. Websphere, holy shit. Everyone feared touching that piece of garbage. And holy crap every page looked the same. Whoever designed that garbage was obviously color blind.
I had no real issues with WebLogic. Websphere....ten foot pole for me.
Weblogic was fine via Cli for me, the UI was slow AF. Websphere... I literally wanted to drive down to ibm and kill them after using it for a few days.
If you want to bring your WLS, tWAS, WebSphere, or JBoss EAP workloads to Azure, we have a home for you at [https://aka.ms/java/ee](https://aka.ms/java/ee) .
Looking forward to the support for Java 17+. We're running a big application on Weblogic and although we're in a migration process, it won't be done anytime soon. That said, Oracle made a similar statement last year, claiming "CY2023". It's kinda disappointing.
Still waiting for the WebLogic 14 LTS version. No roadmap, no planning...
The power of customer demand.
good for them