On 23.10.24 18:53, Roman Shaposhnik wrote:
On Wed, Oct 23, 2024 at 3:50 AM Paul King <pa...@asert.com.au> wrote:
Definately something we should look at. A few folks we'd need to work with to
make that happen. My thinking is let's get Geb over the line first and then we
can repeat for a few other projects if/as needed.
[...]
One question I've got is
this tho: is there enough community left to [at least semi-]actively
maintain it?
I think that gpars should become an overhaul with a tighter integration
into Groovy as language (async/await is one thing here very obviously)
and I think for this it would make most sense to make gpars a submodule.
for example maybe we choose one concept, tightly integrate that in
Groovy and then rebuild gpars different variants based on that. Since
there is now virtual threads and maybe soon something like continuations
in the JVM some things may really become worth rethinking an reinventing
GPars. Maybe most of the DSL will stay the same.
So the story is in my eyes slightly different...
bye Jochen
