I mean I also think you are right. I will observe that Java EE is now Jakarta EE. It is important because it means not much money is to be made by "Java EE" now, So Oracle has dumped it to Eclipse foundation as Jakarta EE.
It has also been sliced and diced in to multiple profiles, popular among them is Microprofile. It can be implemented with Apache tomcat instead of heavier Websphere/ Weblogic etc.
Another thing that happened is container term which in Java world would be Servlet/EJB containers is now associated with Docker containers. And Java enterprise containers fell out of fashion.
All these factor led do Java/Jakarta EE being also ran.
Comments
I mean I also think you are right. I will observe that Java EE is now Jakarta EE. It is important because it means not much money is to be made by "Java EE" now, So Oracle has dumped it to Eclipse foundation as Jakarta EE.
It has also been sliced and diced in to multiple profiles, popular among them is Microprofile. It can be implemented with Apache tomcat instead of heavier Websphere/ Weblogic etc.
Another thing that happened is container term which in Java world would be Servlet/EJB containers is now associated with Docker containers. And Java enterprise containers fell out of fashion.
All these factor led do Java/Jakarta EE being also ran.
And there I was patting myself on the back for not calling it J2EE ;)