That's why I stuck with vi and sh back in the day: I knew they were on every machine I might telnet to (this was before ssh, sigh).
On machines I controlled, I mostly used ksh, but it wasn't available on all machines; I cannot remember if it was the SunOS boxes or the older HP-UX or the Apollos, but there were a few. (csh? Go away. No, just go.)
Nowadays, vim and bash are everywhere I need them to be, even if I have to kludge around some version differences.
My only real gripe about find is the awkwardness of pruning multiple hierarchies. After you've written
On machines I controlled, I mostly used ksh, but it wasn't available on all machines; I cannot remember if it was the SunOS boxes or the older HP-UX or the Apollos, but there were a few. (csh? Go away. No, just go.)
Nowadays, vim and bash are everywhere I need them to be, even if I have to kludge around some version differences.
My only real gripe about find is the awkwardness of pruning multiple hierarchies. After you've written
a few times, and have returned to the previous command to add yet another tuple, it gets a little old.But it works. Everywhere.
(* that I need it)