[nogridbag]

Not a Golang dev, but from your description Go sounds similar to Clojure in that you can kind choose to build your own framework by just picking and choosing your own libraries, e.g. use library X for routing, library Y for templating, etc.

When I was trying to learn Clojure (several years ago... so this info I likely out of date), my understanding was there was a bit of a rift in the community where half the community preferred the flexibility of picking and choosing libs and the other half felt having a "batteries-included" framework would help the growth/adoption of the language. Also, because there was no "goto" framework the libraries were likely not as battle tested.

I'm using Java and unlike the comments in the adjacent thread, using Java doesn't mandate using Spring Boot. There's a bunch of options these days. Personally I'm using Quarkus. Quarkus, like most frameworks, is just a collection of libraries and those libraries follow a "standard" to future-proof your application to an extent. You can still pick and choose what parts you want to use. Want an ORM? Great, include the optional Hibernate dependency. Need to support OpenId connect? There's a simple extension. Nothing really forces you to use the "official extensions", e.g. we're using ElasticSearch but we're not using the Quarkus extension.