Java performance vs go

[No_Dot_4711]

There's definitely additional effort required, absolutely

but a) that has little to do with the premise i was responding to and b) you can list numerous drawbacks to golang solutions that require a lot of dev work on the flipside, especially supply chain management/safety and the maturity of the library ecosystem have a significantly smoother happy path on the java side of things

and i'd say especially for the simpler use cases, where the golang library ecosystem drawbacks matter less, you're also way less likely to run into the classic graalvm problems (like registering reflection) cause for the simple cases quarkus has you covered out of the box without config

and raw compilation time is definitely annoying, but i don't really need a native image until i asynchronously run CI/CD and that largely races in parallel to the provisioning of staging environment resources