Synchronous executor interface
Attila Kelemen
attila.kelemen85 at gmail.com
Wed Aug 9 19:21:12 UTC 2023
Robert Engels <rengels at ix.netcom.com> ezt írta (időpont: 2023. aug. 9.,
Sze, 1:51):
> I also still don’t understand this. virtual threads are moving Java to
> synchronous - they are moving it back to original Java with thread as the
> unit of execution. This wasn’t needed before async arrived and it isn’t
> needed now. Use standard Java thread based concurrency patterns.
>
>
If this argument is valid, then we might as well say that there was a time
when there was C without Java existing. Therefore, Java is useless. A lot
of new patterns have emerged since then, and the ecosystem is a lot bigger
also (of course, that is an argument both for and against adding
something). Also, just because you can technically implement something
without X, doesn't mean X shouldn't be provided out of the box. Here I
would like this in the JDK specifically, because of the interface that can
provide a standard way to communicate between libraries. I'm not saying I'm
stuck without it, but that it would be useful enough to warrant adding to
the JDK. Also, I don't think that this is super urgent at this point,
because it will obviously not be added to 21, and non-LTS releases are of
minor importance for this.
Anyway, I think I will close our debate with this: To simply put, you don't
see much value in it, I do. And at the end of the way what will matter, how
many people find it useful, that we can't really decide now anyway.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20230809/d9085efd/attachment-0001.htm>
More information about the loom-dev
mailing list