When a person curses, it's a direct indication that they are thinking on a lower, more reactive, more emotional level.
The site owner has another site with some pretty good linux/bash tutorials. Props where it's deserved.
Generally I don't like this kinda faux-intellectual and antagonistic writing. Reading this makes me pull out technical jargon or fancy words from my vocabulary like weeds. They use the term coomer which I haven't seen in years. They mentioned an undergrad in econ somewhere, maybe that's what give the boon of confidence?
Anyone else think they may have become sorta like this if things were different? I think that may have happened to me if I was less caring of others... and more hateful of others instead of hateful of myself (still working on that!)
Something interesting is the casual usage of psychology as an explanation, usually where the reason why someone or some people do a thing is because of a keen insight of the writer, where, what people self-report is untrue and what is inferred is true.
They also talk about conspiracy a ton for some reason.
The kinds of thinking really go all around, it really confuses me as how said folk manage to create a coherent understanding. The easy answer is maybe they don't, and I might be inclined to agree, I'd like to try and have a dialogue to see how their brains work.
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.
oh whaaaat! this is so cool, i have not seem any of this before. reminds me of plan9 videos i was watching, dreaming of what could have been...
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.
yo i just installed elvish on my proxmox pve host, kinda confusing but it seems pretty cool, ty for the recommendation!
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
fr fr no capp!