Java 14 is in development, even if it’s still a few months away. Java 12 and Java 13 each came with a manageable number of new features, and thanks to the new release cadence that probably won’t change for Java 14. We’re keeping track of JDK 14 news, so what’s new? Five of the JEPs targeted to JDK 14 are now confirmed and JEP 365: ZGC on Windows is back, once again proposed to target Java 14.
OpenJFX is currently hosted on Mercurial, but with Project Skara in the pipeline and JavaFX already partially on GitHub, Kevin Rushforth thinks it’s time to talk about moving OpenJFX there as well. It couldn’t have come at a better time because Bitbucket announced this week that they are shutting down Mercurial for good next summer.
Two new JDK Enhancement Proposals, or JEP, drafts propose to make changes to garbage collection in the next JDK. One wants to remove Concurrent Mark Sweep garbage collector, since it was deprecated two years ago, and the other wants to make Z Garbage Collector available to macOS users as well. Let’s take a closer look.
Welcome to the newest milestone for Project Loom. Early access for Loom builds are now available, according to the OpenJDK mailing list. Find out what feedback will be helpful to bring this project closer to stability. Project Loom is intended to help with scalability, performance, and delivering Java VM features and APIs.
Oracle and JetBrains engineers proposed to collaborate on a macOS-based graphics rendering pipeline to replace the current one, which is based on the now-deprecated OpenGL. The voting is over and the proposal is officially approved.
The development of JDK 13 proceeds smoothly. As per the JDK schedule, JDK 13 has officially entered its next phase of the development process: Welcome to Rampdown Phase Two. With this, the overall feature set is now frozen and no further JEPs will be targeted for this release. Catch a refresh on what JEPs are targeted for JDK 13.
Project Skara’s goal in July last year was to look into the viable SCM alternatives to Mercurial. It looks like Git is to be OpenJDK’s new home, at least following JEP 357’s proposal. Let’s take a closer at look at what’s going on.
Last year, the JDK team made a call for discussion in order to investigate a number of options for JDK source code management. Is it time to retire Mercurial in favor of Git? We asked our readers and the answer was a definite “yes!”. Today, we revisit the discussion as the JDK team takes the next step and makes the tooling for Project Skara available on GitHub.
JDK 13 is now in Rampdown Phase One. The feature set is frozen and the stabilization repository is open for select bug fixes and late enhancements. Let’s take a look.
About a month ago, Red Hat announced that it will be taking over the leadership for OpenJDK 8 and OpenJDK 11 calling out the need for continued support of the technology and community. But what does this mean for the developer community? We asked our readers and the results are in!
It’s the first Monday of the month and that means that it is time for our monthly recap! From the latest updates on the progress towards Angular v8 to the first look at JDK 13, this month had it all. Let’s take a look.
Time to keep up with the developments happening in Java and in the potential future of the JDK. Let’s take a look at this newly added JEP draft: JVMCI based just-in-time compiler pre-compiled as shared library. What goals for Java does it propose?
What’s new for Java? Discussion and JEP drafts move us forward day by day. One JEP draft suggests a new solution: Keyword Management for the Java language. See what its goal are, what it plans to accomplish, and what potential alternatives there are.
Brian Goetz has submitted a new JEP draft aimed at making data aggregates in Java easier to write, read and correct. Let’s take a closer look.
