JEP-476 module import considered harmful

[Pavel Rappo]

> On 19 Nov 2024, at 14:37, Pedro Lamarão <pedro.lamarao at prodist.com.br> wrote:
> 
> Em ter., 19 de nov. de 2024 às 11:09, Cristian Mocanu <cvmocanu at gmail.com> escreveu:
>  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).
> 
> Optimizing Java for GitWeb-like readers does not seem to me the way forward.
> GitWeb-like products are themselves moving toward "AI powered web IDE" status.

I'll comment specifically to your comment, and not to the original post or follow-up comments from Ron or Brian.

It's not optimising Java for Web/IDE things. It's the other way around: it's making sure one does __not__ need those or any other external things to work with Java. Again, not for this case, but in general: imagine introducing a language feature so complicated and non-intuitive that you'd __need__ IDE support to work with it.

Example: no matter how genius text blocks (JEP 378) are, which they certainly are, I feel like I at times I need IDE support to figure out or remind me how to figure out incidental whitespace.

-Pavel