Brian Goetz says "I was peeking through the URLClassLoader code, and it seems awfully inefficient. If we're so concerned about startup, have we evaluated whether that's a part of the problem? e.g., uses exceptions for control flow, doesn't build maps of what is in each JAR, etc"
Synchronization in URLClassLoader is also extremely coarse grained. Low hanging fruit?
This might be helpful when we are attacking the various warmup problems that stem from the huge amounts of classes being generated by Indy.
I know Claes was looking at stuff like this, so I am assigning it to him.