4 ms·
As a professional gopher, don't. Just a few months ago I replaced an almost 100-line Go "script" with two lines in the Makefile. The fact that Go is great for
by ainar-g 8y ago
As a professional gopher, don't.
Just a few months ago I replaced an almost 100-line Go "script" with two lines in the Makefile. The fact that Go is great for big projects doesn't automatically make it good for everything. Go is for programs, not scripts.
- arendtio 8y agoThanks for your warning :-) My problems come from the other end: My Bash scripts tend to become larger. A few weeks ago I wrote a 'cache' utility function (very useful to cache curl requests for example). A few days ago I wanted to use it in a second script was just about to write a package manager for bash modules... I think that is the kind of situation you are getting into when the line count of a bash script increases and you are trying to do proper software development ;-) So I am not going to build every script in Go from today on, but I would like to learn a bit more on when Go is a viable alternative to Bash.