Yeah, having to take the extra steps to parse strings every time is far superior to objects that can sort, filter, and give you the exact properties you need natively
I mean, if your complaint is a heavier overhead, sure, but for most uses as an interactive shell or for smaller scripts, I don’t really see how that would negatively impact you in meaningful ways compared to having to splice raw text and hope the package maintainer doesn’t decide to add a column in a future update
That might be true if *NIX had another shell with an object-based pipeline, or if PowerShell wasn’t object-based
I’d argue most people who dismiss PowerShell offhand like that don’t understand it particularly well
Most gnu / bad tools are essentially objects, you just have to xarg the column you want
Object orientated anything is pretty terrible
Yeah, having to take the extra steps to parse strings every time is far superior to objects that can sort, filter, and give you the exact properties you need natively
I mean, if your complaint is a heavier overhead, sure, but for most uses as an interactive shell or for smaller scripts, I don’t really see how that would negatively impact you in meaningful ways compared to having to splice raw text and hope the package maintainer doesn’t decide to add a column in a future update