<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 28 Oct 2022, at 23:25, Karsten Silz <<a href="mailto:karsten.silz@gmail.com" class="">karsten.silz@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 28 Oct 2022, at 22:10, Ron Pressler <<a href="mailto:ron.pressler@oracle.com" class="">ron.pressler@oracle.com</a>> wrote:</div>
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">On 28 Oct 2022, at 08:19, Karsten Silz <<a href="mailto:karsten.silz@gmail.com" class="">karsten.silz@gmail.com</a>> wrote:<br class="">
<br class="">
These reasons may have influenced the decision to delay the standardizing of static executables in favor of optimizing Java first.
<br class="">
</blockquote>
<br class="">
I couldn’t find anything in the document that says that the implementation of some condensers will be delayed in favour of others.<br class="">
</div>
</div>
</blockquote>
<br class="">
</div>
<div class="">Sorry if that wasn’t clear: I was referring to the May announcement there:
<a href="https://openjdk.org/projects/leyden/notes/01-beginnings" class="">https://openjdk.org/projects/leyden/notes/01-beginnings</a></div>
<div class=""><br class="">
</div>
<div class="">"So rather than adopt the closed-world constraint at the start, I propose that we instead pursue a gradual, incremental approach. We will explore a spectrum of constraints, weaker than the closed-world constraint, and discover what optimizations
they enable. […] In the long run we will likely embrace the full closed-world constraint in order to produce fully-static images. Between now and then, however, we will develop and deliver incremental improvements which developers can use sooner rather than
later.â€</div>
<div class=""><br class="">
</div>
<div class="">So I understood this as “Leyden will optimize Java first and later standardize fully-static imagesâ€. Am I wrong?</div>
<div class=""><br class="">
</div>
<div class="">And my understanding of the October proposal is that it explains how these goals will be achieved. But it didn’t seem to change the plan of optimizing Java first. Please let me know if I missed something there!</div>
<div class=""><br class="">
</div>
<div class="">
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Karsten Silz</div>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
<div class=""><br class="">
</div>
<div class="">I don’t think you’re wrong in expecting that “standardising static images†would probably not be the *first* deliverable from Leyden, but I do think you’re wrong in concluding that that means it’s *delayed* (e.g. Project Loom delivered JEPs 353
and 373 in JDKs 13 and 15 respectively, so JEP 425, virtual threads, wasn’t Loom’s first deliverable, but it certainly wasn’t delayed by those JEPs). You’re reading “we believe we’ve found a way to deliver value at various points on the road to X†as “X is
delayedâ€, and that’s a misinterpretation.</div>
<div class=""><br class="">
</div>
<div class="">The document suggests that the work on investigating the concept of condensers — the thing that could eventually enable static images — will start right away (and may be done in parallel to developing specific condensers). Obviously, that work
will need to get from where we are today to some point that’s some ways off, but the great news is that we may be able to deliver value on the way there.</div>
<div class=""><br class="">
</div>
<div class="">I think your real question might be, “but I want feature X *now*; could you get there faster?†Like with many other OpenJDK projects, there's probably some “there†that we could get to faster, but that’s usually not where we’d like to end up.</div>
<div class=""><br class="">
</div>
<div class="">BTW, I don’t understand what “optimising Java first†means. The work on optimising OpenJDK is constant; it neither starts nor ends with Leyden. Project Leyden, among other things, will support it.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">— Ron</div>
</body>
</html>