To be fair, a lot of the programs don’t use a single character, have multiple spaces between fields, and cut doesn’t collapse whitespace characters, so you probably want something more like tr -s " "|cut -d" " -f3 if you want behavior like awk’s field-splitting.
This is awesome! Looks like an LPI1 textbook. Never got the certification but I’ve seen a couple books about it and remember seeing examples like this one.
People are hating on Powershell way too much. I don’t like its syntax really but it has a messy better approach to handling data in the terminal. We have nu and elvish nowadays but MS was really early with the concept and I think they learned from the shortcomings of POSIX compatible shells.
I really can’t stress enough how much power and flexibility comes with an object oriented shell, especially with the dotnet type system behind it.
I think most people who hate it just do so either because it came from Microsoft (which… Yeah, that’s understandable), or because it’s a different way of thinking about it (and/or they spent a lot of effort learning how to parse data from strings effectively and hate that it’s made easier?). But love or hate it, it is effective and powerful, and I find myself missing that when working with bash.
Honestly I think 90% of people would never use awk if there was a simple preinstalled command for “print the nth column”
cut?
To be fair, a lot of the programs don’t use a single character, have multiple spaces between fields, and
cutdoesn’t collapse whitespace characters, so you probably want something more liketr -s " "|cut -d" " -f3if you want behavior likeawk’s field-splitting.I never understood why so many bash scripts pipe grep to awk when regex is one of its main strengths.
Like… Why
grep ^nvme0n1 | awk '{print $3}'over just
awk '/^nvme0n1/ {print $3}'Because by the time I use
awkagain, I’ve completely forgotten that it supports this stuff, and the discoverability is horrendous.Though I’d happily fix it if ShellCheck warned against this…
This is awesome! Looks like an LPI1 textbook. Never got the certification but I’ve seen a couple books about it and remember seeing examples like this one.
cut and tr are like the wonder twins of text munging
This is definitely somewhere that PowerShell shines, all of that is built in and really easy to use
People are hating on Powershell way too much. I don’t like its syntax really but it has a messy better approach to handling data in the terminal. We have nu and elvish nowadays but MS was really early with the concept and I think they learned from the shortcomings of POSIX compatible shells.
I really can’t stress enough how much power and flexibility comes with an object oriented shell, especially with the dotnet type system behind it.
I think most people who hate it just do so either because it came from Microsoft (which… Yeah, that’s understandable), or because it’s a different way of thinking about it (and/or they spent a lot of effort learning how to parse data from strings effectively and hate that it’s made easier?). But love or hate it, it is effective and powerful, and I find myself missing that when working with bash.