Regarding nested packages: I've actually seen more nesting in Perl packages than in Java ones. For instance, the java.io package has a twisty maze of relationships but all the classes are in the same package.

One of the features making java package names a little longer is that by convention they're organized so nobody will step on any other namespace. You do this by organizing your code under your reversed domain name. So I work at optiron.com; our code is all under the com.optiron hierarchy. So before you've even applied logic you're two levels deep!

That said, IME once you get to four deep you start getting the hacker equivalent of deep sea diving pressure, forcing you back up the tree to lighter waters :-)

Chris
M-x auto-bs-mode