And most of the newer Java stuff is syntactic sugar, so I’m not sure why that commenter is calling out JVM implementations. I’m guessing they don’t know much about the JVM, since you can compile these higher level syntax tricks down into bytecode just like you might compile more verbose source code.

Static analysis of compiled code with javap might be more difficult, but I’m betting the commenter doesn’t know what that is either.

[–] nik9000 1 points 7 months ago

I think the last new instruction the JVM added was invokedynamic like 10 years ago. I believe they did it so lambdas could be called efficiently. Polymorphic incline cache and stuff.

But the JVM has grown more complex in other ways. The way to force simd instructions is pretty wild, for example.

I don't know enough to call it a mess or not. It works though.

[–] [email protected] 5 points 7 months ago* (last edited 7 months ago) (1 children)

Because Java sucks at taking those features. I mean look at Java's Optional abomination of a class and compare it to C# or Typescript's optional chaining ( ?. ) language feature.

There's a reason Kotlin was created, because Java is still bogged down by all its legacy kruft.

[–] [email protected] 3 points 7 months ago

It still boggles my mind that C# is as good as it is given where it comes from. Java really fucked up with type erasure and never fully recovered imo.