<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 01/09/2023 22:16, Attila Kelemen wrote:<br>
<blockquote type="cite" cite="mid:CAKDaPBfHdPkvJpCA_Zs=xmDsNKhzkdULOvZTV1S5YEtV6_Q+zQ@mail.gmail.com">
:<br>
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>When I wrote "stop using the module system" I'm obviously
talking about the application itself being modular. I would
have expected that you also believe that it would be better,
if applications were modular. Given that I assumed from what
you wrote that you regret the fact that modules were not
added on day 1 (in which case there would only be modular
apps most likely). Yet, this JEP just motivates people away
from modules.<br>
</div>
</div>
</div>
</blockquote>
<br>
I don't think this is the case. Instead I think there is a lot of
potential for a much better story. Modules lend themselves to doing
a lot more at build time and setting things up for simple/fast
checks at startup (think post resolution checks). It's not hard to
think about fail fast if a module requires the "restricted methods
or native code" capability that has not been granted. Combing a set
of modules at link time also has a potentially interesting story
when using jlink to create an application that has an initial/main
module. In that case, you can think about checking capabilities (or
whatever term is introduced) at build/link time.<br>
<br>
-Alan<br>
</body>
</html>