JDK 10: General Availability

http://mail.openjdk.java.net/pipermail/announce/2018-March/000247.html

by tronotonante • 8 years ago

228 110 8 years ago

mail.openjdk.java.net

sadiq2• 8 years ago

Something not mentioned amongst the JEPs on the release email is that this release also fixes a bunch of issues related to running the JVM in a container. I wrote about some of these yesterday:

https://www.opsian.com/blog/java-on-docker/

Relevant JEPs:

https://bugs.openjdk.java.net/browse/JDK-8146115

https://bugs.openjdk.java.net/browse/JDK-8179498

https://bugs.openjdk.java.net/browse/JDK-8146115

suj1th• 8 years ago

Thanks for sharing the blog-post. I use Scala on Docker, and the features/fixes you mention certainly helps me in simplifying my deployments.

dordoka2• 8 years ago

Some support for these was also introduced in JDK 8u131 back in April 2017 [0]. Do you know if these issues are the same ones fixed in JDK 8 or maybe they have now been backported to JDK 8 and 9?

Thanks!

[0] https://blogs.oracle.com/java-platform-group/java-se-support...

sadiq2• 8 years ago

JDK 8u131 and 9 had a few improvements but the changes to 10 increase support.

For example, 8u131 and 9 only supported cpu sets whereas 10 includes support for cpu shares. Available memory detection in 10 applies to the whole of the JVM rather than just the heap on 8u131 and 9.

StreamBright• 8 years ago

Does anybody know which release is going to be the a long time supported release? Should I stay on JDK8 for now?

mavroprovato• 8 years ago

Java 11 will be the next LTS, see here: http://www.oracle.com/technetwork/java/eol-135779.html

So if you care about long term support, you should stay on JDK8

w4tson• 8 years ago

That’s not the advice Mark Reinhold gives. From the talk I saw some give last year he advises moving with the versions.

If it’s one thing we’ve learned in software it’s embrace the change. Little and often is the way to stop technical debt accruing

Tepix• 8 years ago

The next release in September 2018 (JDK 11) will be a LTS release.

WHoWHo2• 8 years ago

Sad var/val (or var/let) didn't make it.

All good Java developers I know make all local variables final to force better code.

mabn• 8 years ago

Does it actually help? After 10 years of java I don't really remember any case where defining local variable as final would catch an error. Though maybe these cases are easy to forget.

WHoWHo2• 8 years ago

From my experience in 20 years of Java, it prevents the reusage of local vars, which mostly is wrong.

   Person p = ....
   p = doSomething(p)
   ...
   p = doSomethingElse(p)

is hard to reason about when it should be

   Person p = ....
   ... lots of code
   Person updated = doSomething(p) 
   ... lots of code
   doSomethingElse(updated)

Which is easier to read and understand. So you might have had bugs that would have been prevented with final, but you didn't attribute to final.

mzl• 8 years ago

For me, it is not about catching errors, it is about documentation.

In the codebase I work on most, all variables that can be marked final are marked final. That means that whenever I see a non-final variable, I know that something tricky is happening and I need to be extra careful in reading the code.

merb3• 8 years ago

var is inside jdk10... http://openjdk.java.net/jeps/286

trzmiel42• 8 years ago

The problem is that "val" or "const" is not.

ygra2• 8 years ago

I think they meant the separate keywords to distinguish "var" and "final var". Personally I like just reusing the final keyword, which for once would actually mean the very same thing in the very same place, with "var" just taking place of the type name. More familiarity, less surprises.

chrislynch423• 8 years ago

var seems like a bad idea to me. One of the things I like about Java is (strong?) typing. Recently learning C# and was put off by 'var'. Why is it a good idea?

flavor8• 8 years ago

I'd advise spending an afternoon trialing Kotlin. It works side by side with existing Java code, has good IDE support (*assuming Jetbrains), and gets you var/val along with a lot of other goodness (data classes, extension methods, etc). At worst you'll have a nice demo for your next tech all-hands.

sorokod• 8 years ago

Release notes: http://www.oracle.com/technetwork/java/javase/10-relnote-iss...

SCdF• 8 years ago

I'm so confused, I didn't even know JDK9 was out yet!

Reading elsewhere they are apparently moving to a 6 month release cycle.

For people using Java in businessey environments, I'd love to hear your thoughts on this. Do you think you'll be able to keep up with the JDK changing twice a year? When I was in this game we were always on versions that were years behind, but maybe this has changed.

BonesJustice2• 8 years ago

This release cycle makes no sense to me. We haven’t even finished migrating all our components to compile with JDK8 yet, though they’ve all been running against it for a while now. We’re barely even discussing moving to JDK9 at this point. What company with a reasonably large software base is going to keep up with a six-month release schedule? Java isn’t a web browser or some other user application. Who would even _want_ to spend the kind of resources required to constantly be testing new JDK releases?

naibafo• 8 years ago

That's why they have LTS releases I think?

akerro4• 8 years ago

This release cycle makes no sense to me. We haven’t even finished migrating all our components to compile with JDK8 yet

Why is it Oracles fault that you keep your components on Java version that has been deprecated and support dropped 4 years ago?

What company with a reasonably large software base is going to keep up with a six-month release schedule?

What? No. That's now how it works. Every 3rd release is LTS and it support time is between 6 and 11 years as so far discussed. Java8 won't be supported after January 2019, Java11 (LTS) will be release in September this year.

Java isn’t a web browser or some other user application. Who would even _want_ to spend the kind of resources required to constantly be testing new JDK releases?

You're not supposed to be testing it. You're supposed to write code to a contract, contract won't or shouldn't change. If you write code that follows implementation instead a contract (let's say you relay on HashSet order - I've seen it), it's your fault. We always make sure we write code that follows the contract. We're migrating our code base to Jigsaw now, after Spring 5 and SpringBoot1.5 were release with updated dependencies. If Spring and Tomcat teams made it available earlier, we would be on Java9 months ago.

bhaavan• 8 years ago

Given that your company is still on JDK7, and is already saying a "fuck you" to new features, I don't think anything will change for you at all. You can continue ignoring newer features, but that doesn't mean everybody should. If they find value, they should have an option to move fast.

jsiepkes• 8 years ago

"We haven’t even finished migrating all our components to compile with JDK8 yet"

Interested to hear which Java API you use which requires special modification in order to be compilable on Java 8?

Usually most of this breakage is caused by the com.sun stuff which isnt public API.

g0510513• 8 years ago

This is the same strategy that wrecked Eclipse and Firefox. Every 6 months is just too quick for most people to feel comfortable, and will cause fragmentation as the 3rd party ecosystem updates things at different rates.

sudhirj• 8 years ago

Not sure that’s how it works. You don’t really need to update anything. Ubuntu runs on y monthly releases, for instance, and sees plenty of enterprise usage. The Linux kernel itself is updated as often, if not more. Google Chrome updates all the time. Ruby does yearly major releases, as do other languages. Go does six months, I think.

Teams in charge of software release whenever they want or can, clients are free to use whatever version whenever they want.

The problems only happen with breaking changes - and I haven’t seen a single case of Java breaking backwards compatibility (not counting cases where users intentionally used or relied on private implementation details).

barkingcat• 8 years ago

I think it makes total sense to have the language evolving on a scheduled basis rather than stagnate.

If your company is only discussing moving to JDK9 now, what difference does it make that JDK10 is out? If you are using the free version, there is no real support. If you are a paying customer, Oracle will support you to the end of time while wringing every last cent out of your company.

What difference does it make if the language keeps evolving? Do you expect the entire world to revolve around you and your company?

mastazi• 8 years ago

They will have LTS versions, the next LTS will be version 11

sumnulu• 8 years ago

Java 8 and 11 has LTS http://www.oracle.com/technetwork/java/eol-135779.html

agumonkey• 8 years ago

Yeah I remember downloading a jdk9 prerelease not long ago and now jdk10 ... does not compute

madmulita• 8 years ago

You want the short or the long answer? We still have major components using java 1.4.2.

firebird84• 8 years ago

We intend to only switch to LTS versions. 8 is LTS, as will be 11. We'll switch a little while after 11 comes out once we believe any release bugs are ironed out (7's release worried me).

Traubenfuchs• 8 years ago

Modern enterprise Java uses Docker. At best, a Java upgrade means changing one line in the Dockerfile.

vbezhenar• 8 years ago

I'm stuck with Java 8, because there's no 32-bit support on newer Oracle JVM and I have to run my code on Windows 2003 servers. I guess it'll be like Delphi 7, best version which will stick around forever. I, personally, don't care about updates. If something works, it'll work.

haspok• 8 years ago

I think that if you still have Windows Server 2003 boxes (for which the official support ended 3 years ago) being stuck with Java 8 is the least of your problems...

b15h0p• 8 years ago

It does not seem to be uncommon to recommend staying away from the non-LTS releases. It is probably not only up to you whether or not your software supports the next JDK release; all your tooling and libraries need to do so as well.

See http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.ht... for more insight.

ptx• 8 years ago

How does Class-Data Sharing – which they've now extended to include application classes – interact with the new "jimage"-format files (e.g. lib/modules) introduced in Java 9? Will the jimage file also be efficiently memory-mapped, making CDS superfluous, or should they be both be applied?

needusername• 8 years ago

There is disappointingly little information available on jimage so it's hard to compare. jimage does require you to be fully modular while CDS does not. OTOH CDS is quite a bit tedious to set up.

ksec• 8 years ago

When will GraalVM / SubstrateVM be part of JRE?

*Still hoping Oracle will be so good to allow TruffleRuby download without all the signing up and agreement.

akerro4• 8 years ago

Some parts of Graal (like ahead of time) were added in Java9 on Linux 64bit, rest of the Graal was added to Java10, but also only for Linux 64 bit. Graal is pretty much workable but there are some edge cases that crash your code or the JVM, eg. Ruby generally works, but Ruby on Rails doesn't.

chrisseaton• 8 years ago

Still hoping Oracle will be so good to allow TruffleRuby download without all the signing up and agreement

This is definitely coming very soon.

mrsheen• 8 years ago

I'd wait for 10.0.1: https://twitter.com/tagir_valeev/status/976293600681115648

ThatHNGuy• 8 years ago

what about OpenJDK with OpenJFX? Building by myself it's an overkill task (it requires Qt for Webkit), especially on more platforms. I think it's a pity there are no public available releases of OpenJDK with included JavaFX out there.

When Oracle will remove it in Java11, it would be even worse

AlphaSite• 8 years ago

Well no, the. It bec9mes just another dependency.

ris• 8 years ago

I agree this is something which should be prioritized, but I don't necessarily think the answer should be to just provide pre-built binaries. I feel really uneasy about open source projects that are almost impossible to build by anyone by the authors - more work should go into making the build process less obscene.

corpMaverick• 8 years ago

Does anyone know how the spring framework will deal the Java versions ?

oweiler• 8 years ago

See http://joshlong.com/jl/blogPost/java-10.html

he0001• 8 years ago

Reading through the comments and I’m amazed how people are so darn negative to this. Most of the time people complain about how old java is and the are much more “modern” options. And now suddenly when they finally picking up the pace, you whine like bunch of kids that lost their candy...

rizalp• 8 years ago

Why is JDK9 & JDK10 is quite huge 197MB? Much bigger than JDK8 which only use 75MB

smackfu• 8 years ago

Does anyone know why java.com only offers to install Java 8 for a desktop user?

fareesh• 8 years ago

I'd be really interested to know if there are folks out there who enjoy Java programming as compared to the alternatives out there today.

Does Java fill any kind of niche aside from maintaining those gargantuan projects that are typical of governments and large corporations?

When I learned Java in the 90s, it was hyped up with the promise of microwaves and refrigerators and televisions and every little thing running Java software.

Instead, the only time I've found myself turning to Java was when I built an IDE on top of eclipse for a custom programming language, a few android apps, a few swing projects for school, and a few socket based projects. When dealing with IOT and smaller hardware, I've found myself using node(js) instead.

I've rarely ever found it enjoyable. The IDEs have been sluggish, the GUI libraries have felt cheap and unpolished, with those clunky diamond shaped radio buttons, and I always found myself writing too much code to do very simple stuff, because every library was wordy and verbose. When I looked at my work, it felt inelegant and cumbersome.

What is Java like in 2018? Are there any good, polished open source projects that work well ? What would make you look at a project and say "I think Java is the most suitable choice for that" today?

JDK 10: General Availability

Related Stories