"While that's not something that most Java developers will, it does mean that the people who are writing high performance servers, or other things where they do want to be able to get down to that level, now have this new facility to basically scale their applications and their frameworks in a way that doesn't require them to change the programming model."Īnother Loom initiative in the latest release is JEP 428, Structured Concurrency, an incubation-level effort to simplify multithreaded programming. "With virtual threads, you can have tens of thousands of Java threads to map to a native thread." "We've taken away the long-standing assumption that there's a one-to-one mapping between a Java thread and a native thread," explained Saab. Another child of Project Amber, JEP 427, Pattern Matching for switch, enters its third preview.įrom Project Loom, there's JEP 425, Virtual Threads, the preview of a lightweight threading implementation to complement the more robust Streams API. In Java 19, these thematic projects are expressed in various Java Enhancement Proposals, or JEPs.Īs part of Project Amber, JEP 405 offers a preview of Record Patterns, a way to deconstruct record values by binding each component to a variable. Loom is about scalability and taking Java scalability to the next level." Leyden is about improving startup time and warmup time. "As an example," said Saab, "the Amber project is a project to work on improvements to the Java language and Java syntax, in order to make it more modern, more succinct, easier to use, and, above all, easier to read and understand. The improvements focused on by the Java community have been organized around specific themes. Thus, the Java development process has become iterative and participatory, even as it allows members of the community to sit out releases while features mature. "We didn't find some magic way of doing three or four years of work in six months," explained Saab. They often surface as preview technologies, to prompt community feedback and adjustment in subsequent releases. Java's accelerated release cycle doesn't necessarily mean that new features appear suddenly. "And so an important thing we did there was offering the Java SE subscription for long-term support, basically making it so that enterprises that want the convenience of staying on one version and just getting updates every quarter, to keep them secure, " "We do realize that not everyone out there wants to be rebasing everything every six months," said Saab. "In the past, they would often have to wait for quite a long time to get anything new in Java, and then they would get too much, all at once," he explained. Saab said the result is being able to get innovation into the hands of developers more quickly than was possible during multi-year release cycles. "There haven't been any delays since we moved to this model, which, as you're probably aware, was not always the case with the previous model that we had." "All of those releases came out at the designated time and date," said Saab. In an interview with The Register, Georges Saab, Oracle SVP of development for the Java Platform and Chair of the OpenJDK Governing Board, said this is the tenth release done under the six-month release cycle. Prior to 2017, the database biz and Java barista waited several years between Java releases, which ended up causing delays and ultimately became untenable amid the accelerated release cycles championed by Google, among others, during the transition from on-premises to cloud computing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |