See also https://blog.cloudflare.com/using-go-as-a-scripting-language-in-linux/#current-state-of-go-scripting https://blog.cloudflare.com/using-go-as-a-scriptin

See also https://blog.cloudflare.com/using-go-as-a-scripting-language-in-linux/#current-state-of-go-scripting https://blog.cloudflare.com/using-go-as-a-scripting-language... and https://gist.github.com/posener/73ffd326d88483df6b1cb66e8ed1e0bd https://gist.github.com/posener/73ffd326d88483df6b1cb66e8ed1... . They explained the direct use of "go run" was not good in some scenario. Is that still applied today? > go run does not properly return the script error code back to the operating system and this is important for scripts, because error codes are one of the most common ways multiple scripts interact with each other and the operating system environment.