I was told that listing all the imports individually slows down compilation or execution, not that this makes much sense. I'm not sure how reliable the source was, and never tested it, but I've taken to condensing the imports manually in my Eclipse environment. Am looking forward to the definitive answer, and am too busy/lazy to try and figure or test it out myself. Just tell me what to do. (I've got a lot else on my plate, thank you.)

ra4king's statement about the compiler being smart enough not to load unneeded code has a ring of truth to it.

"We all secretly believe we are right about everything and, by extension, we are all wrong." W. Storr, The Unpersuadables

Java's import doesn't do anything at all except shorten names. Every class in your classpath is already available -- all import does is make it so you don't have to prefix it with the package. It has absolutely zero overhead at any time.

When you read a code from another programmer you can quickly see which specific classes are referenced,and if anything might be missing, old version etc.So when I look at source-code at my company, I can quickly see what classes and packages are important to that class.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org