perl -lane # process input by line, split into fields, print outputs with new lines, execute code
netstat -planet # show process, extended info, all socket types
ss -pimento # basically every piece of info about live connections
iostat -txyz # extended, omit first report (the since-boot one), omit devices with no activity, log datetime
less -SEXIER
Truncate long lines instead of wrap, quit at eof, don't clear the screen, show ansi color escape codes as colors but escape other ansi escape codes.(The second E does nothing but complete the word)
ps aux
Party time: rsync -rave ssh SOURCE DESTINATION $ man dash | wc -w
10122
If you are running scripts most of the time bash is overkill (batch files don't need things like command completion, history and all that interactive stuff). Don't believe me? $ ls -lAh `which bash`
-rwxr-xr-x 1 root root 1.1M Jun 6 2019 /bin/bash
$ ls -lAh `which dash`
-rwxr-xr-x 1 root root 119K Jan 25 2018 /bin/dashThat's an advantage; Plan 9 provides awk for those use cases. There is a clear separation, and a simple yet powerful language for communication (pipes, file descriptors, and files).
>bash is trying to be a full scripting language these days
Arguably Bash over-did somewhere around the time they added support for TCP connections
exec {FD}<>/dev/tcp/news.ycombinator.com/80; echo GET / >&$FD; cat <&$FDI won't get to this in Oil (without help) but I still think it's valid. The languages have so much overlap that they should just be combined. Of course that's what Perl was (leaving out Make), but Raku and Python 3 seem to have left a hole in that design space.
Shell, Awk, and Make Should Be Combined http://www.oilshell.org/blog/2016/11/13.html
Example Code in Shell, Awk, and Make http://www.oilshell.org/blog/2016/11/14.html
Another example: the modern Bash shell vs the Plan 9's Rc shell. The difference in documentation is over tenfold, with the latter still being more less laden with gotchas:
Having said that, I still love me some sick diff -burN-style mnemonics.