3 ms·
I think the same applies for many of the new breed of command line applications like fd and ag/rg. Being able to use them intuitively trumps ubiquity, speed or
by petepete 10mo ago
I think the same applies for many of the new breed of command line applications like fd and ag/rg.
Being able to use them intuitively trumps ubiquity, speed or features.
- mr_mitm 10mo agoDepends on the use case. If used in scripts, ubiquity and speed can be important. Then again, the output of ss is not ideal for script processing.
- PunchyHamster 10mo agoThat's the problem, it's not good for humans, it's not great for scripts
- PunchyHamster 10mo agoBut it's not tradeoff! You can make default view useful without trading versatility. Another annoying part is not supporting json or even CSV. Some tools got modernized with it (like iproute2 tool set), but for these you might as well do /proc scraping yourself...
- sureglymop 10mo agoThat's true in general. But default view is still subjective. The challenge probably lies in recognizing the larges subset of your user base that would like it to be a certain consistent way.
- yencabulator 10mo agoss is from the same batch of modernization as iproute2.
- fn-mote 10mo agoVery curious what is wrong about the rg defaults. The only one I change is to add `--no-ignore`.
- petepete 10mo agoNothing. fd, rg and ag all work how I expect them to work and the arguments and order fit in with my expectations for modern cli applications. They're recursive, they ignore things I don't care about and I can just give them the string I'm looking for, no path, no -name or --recursive etc. find and grep do similar things but work entirely differently and their args aren't even in the same format.