2 ms·
The JVM can load the same class any number of times through different class loaders -> only the (class, classloader) tuple has to be unique. I guess the reason
by kaba0 5y ago
The JVM can load the same class any number of times through different class loaders -> only the (class, classloader) tuple has to be unique.
I guess the reason they didn’t went the duplicative direction is that java has safe class loading semantics at runtime and due to valuing storage/memory capacity (which was frankly a sane choice, like 10x bigger java projects compile faster than a js project that pretty much just copies shit from one place to another?)