<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="">
Indeed, Archie. There are a lot of folks out there that would like the language to be in the business of enforcing stylistic choices, but this is frequently a misguided motivation. If you want to impose a stylistic preference on your own code, use a style-checking
tool. <br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Nov 19, 2024, at 10:12 AM, Archie Cobbs <<a href="mailto:archie.cobbs@gmail.com" class="">archie.cobbs@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">I'd like to throw out a note of hope...? :)</div>
<div class=""><br class="">
</div>
<div class="">I think there is a reasonable debate about whether star imports are "good" or "bad" but from the POV of language design that debate is made almost entirely moot thanks to the robust ecosystem of style checkers.</div>
<div class=""><br class="">
</div>
<div class="">In other words, this is, in effect, just a policy decision that your particular organization can enforce, just like other style preferences such as whether to allow switch case fallthrough, whether to require curly braces around a one-line if/else
branch, etc. If you don't like star imports, then have them cause your build to fail. Problem solved!<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">In this case, just because (a) Java enables a coding practice you don't like doesn't mean (b) you have to tolerate it in your own organization. The (a) and (b) are two separate issues with two separate debates and two separate resolutions.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">-Archie<br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Nov 19, 2024 at 8:38 AM Pedro Lamarão <<a href="mailto:pedro.lamarao@prodist.com.br" class="">pedro.lamarao@prodist.com.br</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div dir="ltr" class="">Em ter., 19 de nov. de 2024 às 11:09, Cristian Mocanu <<a href="mailto:cvmocanu@gmail.com" target="_blank" class="">cvmocanu@gmail.com</a>> escreveu:</div>
<div class="gmail_quote">
<div class=""> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div style="font-size:small" class="">Knowing that code is being read many time more often than written, I don't think it makes sense to optimize writing an import by hand (which no one does anyway - the IDE writes it for us) to the detriment of introducing
confusion when reading the code outside an IDE (like a GitHub PR review).</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Optimizing Java for GitWeb-like readers does not seem to me the way forward.</div>
<div class="">GitWeb-like products are themselves moving toward "AI powered web IDE" status.</div>
<div class=""><br class="">
</div>
</div>
<span class="gmail_signature_prefix">-- </span><br class="">
<div dir="ltr" class="gmail_signature">
<div dir="ltr" class="">
<div class="">Pedro Lamarão</div>
</div>
</div>
</div>
</blockquote>
</div>
<div class=""><br clear="all" class="">
</div>
<br class="">
<span class="gmail_signature_prefix">-- </span><br class="">
<div dir="ltr" class="gmail_signature">Archie L. Cobbs<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>