Virtual threads delivered. They are like Goroutines but the Structured Concurrency API really makes it better. Will any of this be out of preview for the next LTS release?
Amber is making amazing progress. The exhaustiveness checker still needs improvement, but great job.
Panama looks awesome for projects that have to interop outside of the JVM
If Valhalla really delivers in Java 20 or 21 and value/primitive types provide performance improvements, that will be a home run for the Java team.
Completely pulling virtual threads seems quite unlikely. The preview status just means that the Java devs are warning that they may change APIs. For smaller projects that often isn't a big deal, but for bigger projects that span lots of different developers in different companies, breaking changes are a big deal.
Preview means that the API might change a little, not "not cleared for use in production." It's true that you shouldn't distribute libraries compiled with with --enable-preview, but because virtual threads use the same Thread API, that's not really necessary anyway (in fact, there are some libraries designed for virtual threads out there, including the Oracle JDBC driver).
However, that's not to say there's no risk to using virtual threads in production -- not because they're in preview, but because they're new. New features are more likely to have more bugs than mature features.
In short, you can use virtual threads in production if:
You accept the risk that the API could change somewhat and you might need to change your code.
You accept the risk of using a new feature (regardless of it being in preview).
Who says it isn't cleared for production use? I thought that meant the interface was evolving and not-stable yet, but that the feature itself works and is reliable and has gone through QA.
and specifically "Previewing a feature in the JDK will encourage tool vendors to build good support for the feature before the bulk of Java developers use it in production." i.e. they assume some people will indeed use this in production.
Note that although Virtual Threads are in preview, Structured Concurrency is in Incubator, which is much lower standard: https://openjdk.org/jeps/11
and specifically "Previewing a feature in the JDK will encourage tool vendors to build good support for the feature before the bulk of Java developers use it in production." i.e. they assume some people will indeed use this in production.
What I understand is that preview features are meant for tool developers to ensure proper support once it gets out of preview.
IIRC there is no support whatsoever from Oracle for preview features.
IIRC there is no support whatsoever from Oracle for preview features.
You might be right but I have not seen any evidence to suggest that, nor can I see any reason to assume that would be the case.
However, I cannot find any explicit statement indicating that they will be "supported" although previous preview features have been "supported" in that they have had bug fixes and subsequently had the "preview" label removed.
This is sort of implied in your message, but to be explicit for others: preview status is about more than potential API changes, it’s also about stability. The feature is not production ready and should not be used in production.
Previewing a feature in the JDK will encourage tool vendors to build good support for the feature before the bulk of Java developers use it in production.
which implies Java developers will use preview features in production. There is nothing in that official documentation saying preview features shouldn't be used in production.
Personally, I would prefer they make that clearer.
I do not understand how you come to this conclusion, before to me means "before the JEP gets out of preview" otherwise there wouldn't be any point in previewing it.
90
u/Joram2 Sep 20 '22
Congrats Java team!
Virtual threads delivered. They are like Goroutines but the Structured Concurrency API really makes it better. Will any of this be out of preview for the next LTS release?
Amber is making amazing progress. The exhaustiveness checker still needs improvement, but great job.
Panama looks awesome for projects that have to interop outside of the JVM
If Valhalla really delivers in Java 20 or 21 and value/primitive types provide performance improvements, that will be a home run for the Java team.