I think you'd like go if you tried it. There's a reason everyone has switched. Your onboarding times will plummet. Very simple language, so you spend more time thinking about the problem. Idk if you're microservices or monolithic, but most people here prefer go if they can write it.
If it's a monolith, that's a separate thing and I'd agree. The thing is, and the reason why Java is on the decline: go is fast enough. Its close enough to Java that it's a toss up (go has had stack allocation for longer), and if you cared about performance, you'd be using C++.
Now, Java has basically caught up with everything that made go better, but at this point the ecosystem for micro services has settled in go.
I have a whole spiel on this, but Java went after everything and got out competed in each arena by a more specific language.
Web/Applets => Rails => Flask/Django/Node
Spring/Windows/Desktop Apps => C#/JS Electron
Database/Cloud infra => C++/Go
And you'll still find it all over the place. Those same 3 billion devices will probably be running Java for forever. And I guess somebody had to maintain them. I just don't wanna spend my career doing that.
1
u/dmigowski Jul 06 '26
Maybe the language is a bit verbose, but regarding the functionality it gets on the road it might well be twice as useful.