I do: bash -> js -> (rarely ever get this far) The bash step is fast to write as it subsumes all the process calling / management. JS (or python) is a reasona

I do: bash -> js -> (rarely ever get this far) The bash step is fast to write as it subsumes all the process calling / management. JS (or python) is a reasonable next step, often just a tight cli wrapper around a function to be called in bash that is hard to write in bash / is from a library. I find its normally easier to pack JS dependencies for these one offs than python, but both work. Next step is perf/testing focused. Js works as a great first step here as the Promises & event loop let you get a whole bunch of perf naturally that is a pita to arrange in python. Now you have a program laid out and usage tested that can be re-written in something else for real or percieved benefits (go, bash, c++, rust)