Earlier quoted context omitted.
> Groovy needs two lines (@Grab and import) to get a dependency. Golang only requires the import. Perhaps Groovy needs to be rewritten in Go. I'm not dissing Golang but it isn't even remotely the same. A major portion of the OP content was about using Python instead of shell scripts. Golang is not scripting language. You need to compile for each platform and the code is opaque once it is compiled. Not to mention Gola…
> I'm not sure if you just mistyped I didn't mistype. Go would make a good language for writing dynamic languages such as Apache Groovy in. My own Gro is just one example of such a dynamic language.
Wasn't the whole point of Groovy to have something Ruby-like that was more intimately tied into the JVM ecosystem? Seems to me that Go would be just about the worst imaginable [0] implementation language for that.
[0] Or at least, in the class of extremely poor choices that includes all languages that are not themselves especially targeted to the JVM platform.