I've tried to use and get comfortable with Powershell but it's insistence on types and overly heavy syntax just get in the way for my primary use case for shell scripting. (e.g. quick and dirty hacks)
I don't in fact get tired of unstructured data and the limitations of the shell like basic data structures because nine times out of 10 the data I have to work with in a shell is exactly that. Unstructured and basic. Not because of the shell but because the source of that data provides it that way.
Powershell with it's intense focus on fancy datastructures makes something like
sed '/foo/d'
unecessarily hard and that's exactly the sort of thing I use my shell for.
If I want something more powerful for working with structured data I'll use Python or Julia.
Yeah but sed isn't present by default in Powershell. in Unix systems it is and Powershell's ecosystem makes the approach sed uses a second class citizen.
I don't in fact get tired of unstructured data and the limitations of the shell like basic data structures because nine times out of 10 the data I have to work with in a shell is exactly that. Unstructured and basic. Not because of the shell but because the source of that data provides it that way.
Powershell with it's intense focus on fancy datastructures makes something like
unecessarily hard and that's exactly the sort of thing I use my shell for.If I want something more powerful for working with structured data I'll use Python or Julia.