3 ms·
It has everything to do with Java, though not memory. It exploits Java's write-once-run-everywhere feature as well as the decision to initialize classes, includ
by larsrc 5y ago
It has everything to do with Java, though not memory. It exploits Java's write-once-run-everywhere feature as well as the decision to initialize classes, including running code, on load rather than on first instantiation.
- watwut 5y agoClasses are loaded when they are about to be used for the first time.