I think the problem is testing. If you use a tool to convert one language to another, you have to check that the result works, which involves a lot of testing, possibly as much as you had to do to get the original working in the first place. So it's expensive.
It will usually be cheaper to leave your original Java in place, writie new functionality in Go and integrate the two together. You can do that using web services, gRPC, a Service Bus or whatever. This is pretty much the way that Java replaced COBOL. A common trick in the beginning was to put a layer of Java in front of a COBOL solution to provide a web interface. Extra functionality could then be written in Java. Some of those COBOL solutions are still running, hiding behind a Java app. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
