Earlier quoted context omitted.
Yes, arguably a better decision than writing it in golang to begin with.
Go is better than Java any day of any week if startup time or memory footprint are of any concern to you at all. Also Java is OO which is... terrible to say the least.
In 2021, the AOT free beer exists, as do JIT caches.
As for OO model, I rather be able to understand which interfaces a type implements by looking at it, instead of producing compiler errors, or have a type by accident supporting a single method interface with complete different semantics.