[dimes]

Java and Kotlin are both great languages. I do wish it was simple to build / run like Go though. Dealing with gradle is a huge pain. The only reason I use Go over Kotlin for personal projects is that setting up and maintaining a gradle project is quite a chore.

[kitd]

Go is the most practical language for professional development out there atm IMHO, especially for larger projects. The language has it's quirks and Java's ecosystem is insanely huge, but Go hits the sweet spot between time-to-value, "SO-searchability", and performant end-result.

[oweiler]

Just use Maven. Works very well w/ Kotlin.

[blandflakes]

Maven is IMO the best choice for Java and Kotlin, but even maven is stupidly complex. It's sort of maddening that all JVM languages seem to suffer from clunky build tooling, though I'm certainly glad that they work as well as they do.

[hackerm0nkey]

I like the stability of Maven, despite XML and people complaining about it's complexity, I just find it stable enough and does the job quite well.

For one of my clients, we created lots of similar microservices, similar setup but slightly differ. What I did was creating a template using maven archetypes so spinning up a new microservice for a new piece of work or simply to try something out or an ad-hoc job is a matter of seconds, so setup time is stopped being a hindrance to start something new.

Also these days there are quite few tooling that supports project generators which can give you a bit of setup to start from.