> Certainly beclowns one of the biggest arguments for Java
No, it just makes clowns of the OpenJDK teams. There's no good reason to write Base64 implementations in assembler. The idea that native Java isn't fast enough to process Base64 in the kinds of volumes Base64 is used in is completely absurd. What the fuck were they thinking? And if they are going to implement this why wasn't it subject to rigorous review and testing?
I'm not impressed with the Java back-end these days. I found changing the garbage collector from the default to the "old" one (serial - also known as -XX:+UseSerialGC) was enough to cut memory usage of an application I was using that was typically using a gigabyte of RAM by... 85%. What's the downside? You might possibly notice tiny pauses from time to time. How the hell do they blow up memory usage by 8X just optimizing a GC? Why would they even release one that does that, let alone make it default? Jesus, I know RAM is/was cheap (2 years ago), but a gigabyte for something whose C equivalent uses maybe 50Mb?
Java needs better quality control. I suspect though that between burnt out demoralized Oracle devs being the primary developers and, in different directions, .NET, and Rust/Go, taking away interest in what was the flag bearer for managed code, it's not going to improve. If only .NET wasn't so Windowsy.