Gonna try nushell soon as that seems even more productive.
its all a bunch of loops and string manipulation in the end. in fact, awk can handle a whole lot of it too! and octave... and others, lol; so long as it does not turn into the python2 to python3 fun we've had in the past and we have some stability between versions; this is why i still choose bash (and the whole gnu binaries)
edit (formatting i hope, and python)
Blegh, now I have to do some digging...
I think the one that catches me off guard the most is:
export FOO=bar
BAZ=qux
Is now $env.FOO = "bar"
BAZ = "qux"
It makes more sense the nu way, but old habits die hard. $ [1, 2] | math max
2
And here are some strings: $ ["a", "c"] | str join "b"
abc
And there are tables $ [
{name: "foo", value: 6},
{name: "bar", value: 9}
] | where value > 7 | get name
bar
And that's about as weird as the types get.For short snippets, better to read, understand, and translate as you type.
For some shell integrations or environment setup tools, use fenv or babelfish.
For scripts of any length, just save it and run it. The shebang'll invoke bash or whatever is needed.