Future of sh scripts

[LiorLieberman]

We are starting to accumulate a lot of sh scripts (lots of them are generated) - do we want to move some of this to Go?

Although the scripts are not in the critical path, it is relatively hard to understand complex logic in bash.

[BenTheElder]

We should minimize the complexity in the scripts, but I don't think everything should be ported to go either, some things are much harder to read and implement correctly as a go program (e.g. simple piping between a few utilities).

I think as an umbrella issues this is ~unaddressable, and we should propose specific things to rewrite in Go.

[LiorLieberman]

Do you have anything in mind wrt to what should be in go and what's not?

I am happy to have some of the future scripts I personally do in go and not sh but I think that the project could probably benefit from some guidance (otherwise agent generate not so easy to read .sh files)

BTW this came from Bowei Du (@bowei) 's comment on #693