Personally I've had the exact opposite experience with Spring Boot. To me it feels like they've basically had to metaprogram their way out of the limitations of

Personally I've had the exact opposite experience with Spring Boot. To me it feels like they've basically had to metaprogram their way out of the limitations of both the language and the underlying APIs which are extremely verbose and obtuse. Every time Spring makes something more convenient, it also removes some static guarantees. Dependency injection issues fail at runtime instead of compile time, but that's not anywhere near the worst of it. Autoconfiguration in particular seems nice at first but can cause all sorts of weird issues. I once had a situation where we added RabbitMQ, and some other JAR started trying to bind to a queue that didn't exist, but the framework was swallowing that exception and it took hours of screwing around in the debugger to figure out what was going on. That sort of thing simply doesn't happen with Go in my experience. Or probably Dropwizard, honestly.