[viraptor]

Same. I've had to do tiny tweaks to my scripts when updating recently, but I'll take fixing those 2 lines over trying to maintain a script full of callouts to jq, weird quoting, carefully manually managed dictionaries, etc. Nushell is already amazing for devopsy usage.

[bruh2]

Do you mind elaborating on your last point? I'm intrigued by nushell and I'm doing devopsy work, I'll give it a try now but I'd love to hear how you use it and learn from it!

[viraptor]

It makes relying on "shell scripts" much easier. Almost entirely gets rid of explicit whitespace handling in variables. Has proper types, so doing some math is safer. Has built-in dictionary / array / tree value support. Has better error handling.

In practice that means gluing together many tools, especially json/yaml/network-related is easier and you have better safety around it all. You can have proper, reusable functions too.

Each script I rewrote from bash to nushell that basically strings together many AWS calls is ~2-3x shorter now and more readable.

[bruh2]

That sounds promising. Did you use it in a team? If so, how well did they receive your avant garde shell language?

Also, have you tried other alternative shells like xonsh?