There isn't a ton about Java's syntax to be super opinionated on, compared to Go, simply due to how unique Go's syntax is.
My main problem with Java code is that it's too hard to read due to endless variables\classes etc names and such. It's almost like reading some Oracle's documentation rather than reading code.
Golang date formatting on the other hand... I still mad an whoever is responsible for this.
All java code be lie `public static void SomeReallyLongNameDescribingEverthing42 implements SomeOtherEvenLongerName`
For me it's 10 times harder to follow than Go's `if err` blocks (which I actually do appreciate most of the time).
CamelCase makes it even worse. Short CamelCase is quite okay, but the longer it gets, the harder it on my eyes.
But even with short naming it still like 2-3 words just to name a function. wtf.
1. snake_case - best of the best. words are separated, easy to read even if the words are not in english or latin
2. ShrtCmlCase - worse than snake. Pros: quite short, does not take whole monitor width. Cons: requires additional thinking and some sort of in-team guidelines. Very opinionated.
3. JavaCamelCase - worse than ShrtCmlCase. Pros: you can put in and describe anything in a single name of a class\variable. Cons: you spend too much attention on reading rather than analysing the program.
I can understand why Java uses long names though. Its oop and enterprise nature is to "blame". This kind of naming is unavoidable when you are building a giant monolith with hundreds or thousands of classes, all kind of inheritance nuances and trying to have all names actually mean and describe something.
As I said earlier - all are very subjective topics.
Excuse me but Java? This is as subjective as it can be.