Tell HN: Please don't print –-help to stderr in your CLI tools
This is going to sound snotty, and I'm not really trying to be, but... Unix and its derivatives were made for people who sort of knew what they were doing.  The reason you pipe exceptional events to STDERR is so the STDOUT output, if it exists, can flow into the next command in the pipe.  Asking for help is an exceptional event.  If you want the error output of a Unixish (linux, macos, solaris, etc.) machine running bash to be lessable, re-direct it to STDOUT with `2>&1`.  You probably shouldn't be touching the shell if you don't know what that does.  These tools were developed assuming the users would have a basic understanding of the system they were running on.<p>The GNU Project has published tools of varying quality, based on who was around to write the tool, debug it, give feedback, etc.  It is not the exemplar of high quality software.  (But it's far from crap.)  The important bit about GNU (and any other software) is that it was written to adhere to their uses.  Other people have different requirements.  Telling people to "write your software like GNU writes their software" is to misunderstand personal agency and one of the major points of open source software.<p>Your comments sound like you're saying "Software freedom means you're free to write software the way I want you to write software."<p>No thank you.