[vessenes]

What would you like to see?

I’d guess there’s a solution to almost any set of priorities you have for shell scripting.

The domain space is extremely challenging: by default, executing any program on behalf of the caller using arbitrary text inputs, and interpreted.

All modern shells allow calling of literally any binary using the #!/usr/bin/env randombinary incantation.

Upshot: bash has its place, and while some of that place is unearned inertia, much of it is earned and chosen often by experienced technologists.

In my case, if I’m doing a lot of gluing together of text outputs from binaries, bash is my go-to tool. It’s extremely fast and expressive, and roughly 1/4 the length of say python and 1/8 the length of say go.

If I’m doing a lot of logic on text: python. Deploying lots of places/different architectures: go