18 ms·
Exactly - OS X is Unix(tm), but davexunit's complaint is that the term "Unix commands" implies "commands that will work on all/most UNIX/POSIX systems", not "co
by chimeracoder 13y ago
Exactly - OS X is Unix(tm), but davexunit's complaint is that the term "Unix commands" implies "commands that will work on all/most UNIX/POSIX systems", not "commands for a single OS that happens also to be a UNIX".
- pjmlp 13y agoWhich most likely only happens because the majority of HN users only know either GNU/Linux or Mac OS X as UNIX and never really used the big commercial ones. Every time someone mentions here how POSIX and C are portable across UNIXes, I have recolletions of maintaining code full of #ifdefs to make it work across such "portable" systems. Not to mention how nice the Makefiles used to be.
- blueblob 13y agoI agree with the complaint too but not only are many of these commands mac only but in addition to that, they are not less commonly used (ex vim). I feel like I could have gotten quite a few less commonly used tools by ls /usr/bin/|sort -R|head In my opinion it was a poorly named article with just as poor content. Many of the descriptions of the commands were not good ("lsof: godlike"). Better descriptions could generally even be found automatically: man lsof|grep NAME -A1 -m1|tail -n1
- danielrm26 13y agoYou're being that guy.
- lost-theory 13y agoEven easier way to get short descriptions of commands: whatis lsof apropos lsof
- blueblob 13y agoMuch better than my way. Formatting is nicer and I was using GNU specific flags for grep. :-(