News for hackers. Stuff that matters.
Re:Minecraft removing obfuscation in Java Edition by mort96 on Thursday October 30, 2025 @04:25AM (#45757607)
So we're not talking about runtime performance, but some minor improvement in loading times? I assume that once the JVM has read the bytecode, it has its own efficient in-memory structures to track references to classes rather than using a hash map with fully qualified names as keys
Re:Minecraft removing obfuscation in Java Edition by swiftcoder on Thursday October 30, 2025 @05:03AM (#45757823)
Proguard was heavily influenced by the needs of early Android devices, where memory was at a real premium. Reducing the size of static tables of strings is a worthwhile optimisation in that environment
Re:Minecraft removing obfuscation in Java Edition by mort96 on Thursday October 30, 2025 @05:27AM (#45757970)
Okay but we're talking about Minecraft on desktops and laptops, where the relevant optimizations would be runtime performance optimizations, no?
Re:Minecraft removing obfuscation in Java Edition by swiftcoder on Thursday October 30, 2025 @12:29PM (#45761860)
Probably, but proguard tends to bundle the whole lot together
Re:Minecraft removing obfuscation in Java Edition by saagarjha on Thursday October 30, 2025 @04:34AM (#45757653)
The names need to be stored somewhere because they are exposed to the program that way
Re:Minecraft removing obfuscation in Java Edition by mort96 on Thursday October 30, 2025 @04:38AM (#45757673)
They have to be stored somewhere, but they don't have to be what the JVM uses when it e.g performs a function call at runtime. Just having the names in memory doesn't slow down program execution.
Re:Minecraft removing obfuscation in Java Edition by saagarjha on Thursday October 30, 2025 @04:44AM (#45757720)
At runtime this is going to be a branch instruction yes
Re:Minecraft removing obfuscation in Java Edition by throwaway2037 on Thursday October 30, 2025 @10:45AM (#45760599)
Even a hash map with fully qualified names as keys wouldn't be so bad because Stirng is immutable in Java, so the hash code can be cached on the object.