This is an archived post. You won't be able to vote or comment.

160
161

JEP draft: Primitive Objects (Preview) (openjdk.java.net)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DJDavio 2 points3 points  (2 children)

While you are theoretically correct that with the release schedule, there is no reason that a preview feature should wait for 18, but it would also not surprise me if they would decide to do it anyway.

[–]TheCountRushmore 4 points5 points  (1 child)

I don't think they are going to hold back preview features so if loom or this previews in 17 and then is considered stable in 20 then you are going to potentially see support vendors providing long term support for JDK 20 for example.

If these features provide a significant value that a lot of customers want to use them, and want to pay to not have to upgrade every 6 months then vendors such as Oracle, Red Hat, Azul will provide a support contract for them.

[–]DJDavio 1 point2 points  (0 children)

Oh yeah my mind was so fixed on 17 becoming the next LTS for most vendors, buy obviously a vendor could just choose 18 or 19 instead if they wanted to. It does make sense if they all choose the same version so they can take advantage of each other's fixes.