PERL,INGRES,PROGRAMMING

  About time. Spring had it for ages, and was one of its advantages over Jakarta. Will the new initializer turn the tide in Jakarta's favor? Of course it is not that simple. In  "Jakarta vs Spring - The War Goes On"  we saw that there's many aspects of a framework that will drive the decision of sticking or foregoing. But certainly as small as a project initializer's role can be, it nevertheless can make a big difference. https://www.i-programmer.info/news/80-java/16296-jakarta-ee-gets-its-own-project-initializer.html

  In a very interesting webinar streamed live as part of the recent JConference, Antoine Sabot-Durand talked about "hostility" between J2EE/Jakarta and Spring and the differences between them from decades ago to the recent times. Antoine is a Java Champion. He is also the CDI 2. 0 spec lead, involved in Microprofile and various projects linked to CDI ecosystem development and thus Jakarta EE. full article : https://www.i-programmer.info/news/80-java/16150-jakarta-vs-spring-and-the-war-goes-on.html

 Helidon, the open source microservices framework by Oracle, has been updated to version 3. At the same time a new side project, Helidon Nima, introduces virtual thread support. Helidon sprang up back in 2018 from the lack of agility of Java/Jakarta EE in building microservices. Sure you could do that, but not in the most efficient way. Thus at Oracle they thought of a framework designed from the ground up for building microservices would be more efficient. In order to stay close to the Java EE spirit, Helidon was made to implement the Microprofile standard, widely used in Java EE environments. full article on i-programmer: https://www.i-programmer.info/news/80-java/15782-helidon-for-microservices-flies-high.html

 After a lot of iterations and false starts in terms of dates, Jakarta EE 10 is finally here and primarily focused on the Cloud and microservices. Jakarta EE finds itself mostly used in an Enterprise setting. That property is embodied in its name after all - EE for Enterprise Edition. Born in 2017 out of Java EE when Oracle contributed it to the Eclipse Foundation, it was subsequently relaunched as Jakarta EE as well as open-sourced. What it essentially represents, is Java's ability of modernizing, but at the same time keeping ties with the past - a quality highly sought after by those enterprise environments. At its core Jakarta EE is a both a framework and a collection of APIs mainly for developing Web services as well as enabling interoperability between distributed systems. Its versatility lies in that, while you can use it in building microservices, you can also use it in developing monoliths. In fact, Jakarta EE underpins many such infrastructure technologies: full article on...

Quarkus, the Java framework for microservices initially released by RedHat in March 2019, has reached version 2.7.1. But before looking at what's new, let's take a look at what Quarkus does differently and how it contributes to the current popularity of Java. Describing Quakus as a "Java framework for microservices" isn't 100% accurate. Despite the fact that Quarkus was created with microservices in mind, you can also build monoliths with it. Also, while Java is the primary language, you can write Quarkus programs in Kotlin and Scala as well. Quarkus, together with Micronaut and Helidon, is part of a new league of open-source frameworks that have sprung up in the last few years in order to boost the usage of Java in the microservices world. Java supremacy in this arena was under threat due to the bloat that existing frameworks were burdened with - hundreds of class files required, resolving dependencies at runtime, use of reflection, large memory footprint, extend...

  This survey comes from the Eclipse Foundation and provides technical insights into enterprise Java that give answers to questions like which Java based framework is on the rise, whether Java is used for Cloud native development and much more.   Jakarta EE provides a way to modernize infrastructure and reuse the developer pool of the aging(?) Enterprise Java developers in a new setting. We saw something like that in   Vaadin Reaches Version 21 , about the Vaadin framework which supports using the Java stack for writing both the back and front ends of Web applications, without having to learn Javascript or another client framework like Vue or Angular. This is an obvious advantage for those working with long-established code which albeit reliable, is that agile compared to lighter and more modern software development shops. full article on i-programmer.info