You really should not have started with spring and jee

Not understanding why they exist is the first error trying to sell to enterprise.

Seeing how .Net is being sold to enterprises without such libraries I would say that they exist because business happily buys into any promise that something increases productivity even if that is just salesmen's lies. But it requires good salesmen not good engineers.

Actually it does have many of those libraries, they just come with a different name, or in commercial only form, without the FOSS variants from Java.

Avoiding the necessity for libraries like many of these would be a key success criteria for a new language were I judging.

Then don't expect to actually take over Java on the domains it owns.

Why Java devs automatically assume that every new language is made to overthrow Java/C#? They might still to provide better development in a particular domain. Go or Python or JacaScript are good at rivaling Java at mainstream language, and so what?

Because that is what the "every new language" crowd keeps selling, without understanding how they got there.

I know people who would be sold on NO JEE, NO Spring, NO Hibernate. I am one of them. :)

I have to say if they add generics without type erasure to go then Java is likely in trouble.

A language feature alone doesn't replace an ecosystem with 25 years of production experience across platforms that aren't even supported by Go.

After getting generics, Go still needs to offer JFR/JMX/VisualVM like monitoring and dynamic code loading capabilities (Go plugins are very limited), JEE/Spring like Web tooling, Liferay/AEM/Magnolia like CMSs, an OS of its own and real time GC, card chips, M2M hardware gateways, printer enterprise configuration appps, and plenty of other use cases that many on HN seem unaware of its existence in enterprise scenarios.

Isn't Kyocera, like, a printer company?

Yes it is, and those printers support Java for customised enterprise solutions.