Every Monday we take a step back and look at all the cool stuff that went down during the previous week. Last week, was an amazingly busy one! For this reason, we decided to include, in addition to the top 5 news from last week, some “honorable” mentions. We wouldn’t want to neglect anything that went down the previous week!
JDK 11 is shaping up to be a really great version. How do we know that? There are 13 JEPs targeted to JDK 11 so far. The latest “family” member is JEP 333. Although it’s still experimental, it’s certainly nice to see ZGC on the list. Let’s have a look at this JEP.
What’s going on with JDK 11? We’re going to take a look at how this version is moving along, including a look at the new JEPs.
At the beginning of each week, we take a step back and take a look at all the cool stuff that went down during the previous week. It has been another busy week in the tech world with the list for JEPs targeted to JDK 11 getting longer, the release of IntelliJ IDEA 2018.2 EAP, the JAXenter survey on frameworks results coming out and much more.
May is shaping up to be a busy month for JDK 11 now that three more JEPs are targeted to the next Java version. In this article, we’re going to have a look at each new JEP and make a quick summary of what’s targeted to JDK 11 so far.
Every Monday we take a step back and look at all the cool stuff that went down during the previous week. Last week we had a lot of important and interesting news going on in the technology world; Node.js 10 was released, we welcomed a new index to the family, we had a fun review of 5 things we can hate about Go and the list goes on.
Java 10 was released less than a month ago but thanks to the new six-month cadence, all we can think of right now is Java 11. Speaking of the next Java version, Public Review Specification is out — you’ve got until May 7 to download it.
It’s been a long time coming! The Java SE modules that contain Java EE technologies have been annotated as deprecated for removal in JDK 9, so this is hardly news. However, removing the Java EE modules is not without risks.