If you prefer to go without generics, it is your choice. But in this case you will hardly write less lines of code than in language with generics.

I agree with you that Go2 has some questions raised. But my main question is different: do they guarantee strong backward compatibility with what they have done in Go1... it seems the answer is not that easy and straightforward for now.

About Java GC you are just wrong. There is no silver bullet in garbage collecting. Anyone who states that he has one best GC for all types of tasks either intentionally lies, or doesn't know the subject. The reason why Java ecosystem receives new GCs is because people want to solve broader range of tasks. I swear Go GC can't reasonably handle multi terabytes heap filled with small objects with millisecond scale pause times. And Java ecosystem provides such option.

OOP is very simple yet powerful mental framework, which if used properly, could give you great benefits in creating good maintainable systems. As I stated, it's my personal preference to use language which have OOP and it's not something I want everyone to agree with.

You can have Java native binaries with GraalVM if you like, it's not something unusual for Java these days.