3 ms·
palish has a point to the extent that lsof is so infrequently used that it would do no harm to give it a more descriptive name. Nonetheless, I entirely agree w
by tome 18y ago
palish has a point to the extent that lsof is so infrequently used that it would do no harm to give it a more descriptive name.
Nonetheless, I entirely agree with you about ls, and about sticking to the conventions that have developed around unix.
- 11ren 18y agoThere's a tribal aspect, too; not to mention jargon as a barrier to entry. And what professional wants to forgo hard-won knowledge? That said, I kind of like the weird names, esp grep. (Wasn't that in Stranger in a Strange Land or something?) But I do object to inconsistent options. One example is: mkdir -p a/b/c This will make all three nested directories, if needed; but there is no equivalent: mv -p x a/b/c/y There also isn't: cp -p a/b/c [1]. You have to create the nested destination directories (a/b/c) first. [1] cp has a -p option, but with a different meaning... BTW: It would be nice if HackerNews had the `` markdown of Reddit for inline code. There's been a bit of code sharing recently, and I like that in a "hacker" site.
- palish 18y agoFor code, use two spaces at the start of the line. like this
- 11ren 18y agothanks, I know. I referred to inline code.
- gaius 18y agoGrok, you're thinking of.
- 11ren 18y agoyes! thanks,
- d0mine 18y agoInconsistent options are like irregular verbs in English (the most frequently used verbs are both ancient and irregular as a rule).