Doesn’t the logic of the second third screen cap on veganism apply to their logic on cursing? I’m not taking the easy route linguistically, ergo my verbal chasteness is a sign of my intellectual/moral superiority.
Powershell uses a structured data pipeline, as does elvish and nushell and many others. I don't think fish does, it's trying to be mostly POSIX-compliant except where they don't agree with POSIX. I might be wrong about that it's been a long time since I used fish.
Feel free to keep reading my ramblings but the landing pages for both elvish and nushell that I linked above illustrate the power of structured data pipelines, in particular nushell:
Show
Accomplishing something like this with a flat text pipeline like bash would be much longer and far less readable.
POSIX-compliant shells use plain text in their pipeline, which means that any output you pipe from one command to the next has to be done so in either plain text or a format the consuming command can process. What that means in practice is that unless the consuming command has been designed specifically to consume the output from the preceding command in the pipe, users have to do a lot of string manipulation with tools like awk, sed, or grep to structure the output from one command into a format that can be consumed by the next.
Where it really shines is when interacting with APIs that expect to use structured data in their interfaces, as you can just pipe data from one to the next without worrying about restructuring it. It's why PowerShell was created--unlike POSIX-compliant OSes, Windows is built on the component object model, and every API built into the OS already used structured data.
The web is built on structured data (json, xml) as well, and that lucky coincidence made powershell a much more useful shell for over-the-wire API interaction than bash et al.
It's not that you don't have to restructure data that you pass through the pipeline with modern structured-data-pipeline shells, you definitely still do. It's just that restructuring that data is trivial because you don't have to use a textstring manipulation tool to re-construct the output structure from the flat text pipeline, you can access that output structure directly.
Of the examples I gave above, PowerShell's probably the most accessible (in terms of tutorials and whatnot), I ran it as my shell on linux for a couple years before switching to Elvish.
hell yeah comrade. it's a little weird to get used to but I like it. I don't use the object pipe that often in interactive use but it's killer for scripts
deleted by creator
Doesn’t the logic of the
secondthird screen cap on veganism apply to their logic on cursing? I’m not taking the easy route linguistically, ergo my verbal chasteness is a sign of my intellectual/moral superiority.deleted by creator
Crap I meant the third capture
what a piece of shit
also:
pick one tech bro
also bash tutorials are inherently conservative. embrace structured text, reject reactionary 40-year-old-shell fetishism
Finally someone gets it, we need more tutorials in the woke Fish shell instead of "how do I do if statements again in Bash" /j
deleted by creator
Powershell uses a structured data pipeline, as does elvish and nushell and many others. I don't think fish does, it's trying to be mostly POSIX-compliant except where they don't agree with POSIX. I might be wrong about that it's been a long time since I used fish.
Feel free to keep reading my ramblings but the landing pages for both elvish and nushell that I linked above illustrate the power of structured data pipelines, in particular nushell:
Accomplishing something like this with a flat text pipeline like bash would be much longer and far less readable.
POSIX-compliant shells use plain text in their pipeline, which means that any output you pipe from one command to the next has to be done so in either plain text or a format the consuming command can process. What that means in practice is that unless the consuming command has been designed specifically to consume the output from the preceding command in the pipe, users have to do a lot of string manipulation with tools like awk, sed, or grep to structure the output from one command into a format that can be consumed by the next.
Where it really shines is when interacting with APIs that expect to use structured data in their interfaces, as you can just pipe data from one to the next without worrying about restructuring it. It's why PowerShell was created--unlike POSIX-compliant OSes, Windows is built on the component object model, and every API built into the OS already used structured data.
The web is built on structured data (json, xml) as well, and that lucky coincidence made powershell a much more useful shell for over-the-wire API interaction than bash et al.
deleted by creator
thinking about it more, a correction to my post:
It's not that you don't have to restructure data that you pass through the pipeline with modern structured-data-pipeline shells, you definitely still do. It's just that restructuring that data is trivial because you don't have to use a
textstring manipulation tool to re-construct the output structure from the flat text pipeline, you can access that output structure directly.Of the examples I gave above, PowerShell's probably the most accessible (in terms of tutorials and whatnot), I ran it as my shell on linux for a couple years before switching to Elvish.
deleted by creator
hell yeah comrade. it's a little weird to get used to but I like it. I don't use the object pipe that often in interactive use but it's killer for scripts
deleted by creator
deleted by creator