On 09.05.22 22:13, MG wrote:
Hi Jochen,
our code certainly creates a lot of (short lived) class instances*, but
we do not dynamically create new classes, so the overhead of creating
the initial Indy callsites should only be incurred once at the
beginning, and then should no longer play a role. S
Hi folks,
We still have a few things on our TODO list to improve Groovy 4, like
performance and some regressions, but we also need to start planning
for Groovy 5. I am happy for broad ranging discussions on Groovy 5 to
begin, so feel free to comment, but I don't expect many of us will
have time to
Hi Folks,
Any other updates/comments before I submit our latest board report?
(Due soon)
Thanks, Paul.
===>8==
## Description:
Apache Groovy is responsible for the evolution and maintenance of the
Groovy programming language
## Issues:
No issues requiring board attentio
One thing to consider is the EOL schedule, of course. Oracle
advertises[1] "extended support" for its Java customers for:
JDK version
until
8
2030*
11
2026
17
2029
* "The Extended Support uplift fee will be waived for the period March
2022 - December 2030 for