News for hackers. Stuff that matters.
Re:The Poetics of CLI Command Names by frank2 on Tuesday June 09, 2020 @09:44PM (#23472987)
I guess it won't hurt to explain the joke.

The Mac has what is sometimes called a "BSD userland" with the result that cp, rm, ls, grep, etc work basically like they do on FreeBSD. But some Mac users prefer the GNU versions of those commands. To avoid breaking scripts that depend on the BSD behavior, when Homebrew installs the GNU versions, it names them gcp, grm, gls, ggrep, etc.

Re:The Poetics of CLI Command Names by skissane on Wednesday June 10, 2020 @03:06AM (#23474711)
Not just macOS. At my first full-time job, I was introduced to Solaris. I had been using Linux for years, and been using GNU utilities for even longer (through EMX, which is like Cygwin but for OS/2). And the lack of options I was used to from the GNU versions infuriated me. They told me, "just put a g in front". Although it wasn't a standard part of Solaris install, the sysadmin had installed several of the GNU utilities (from sunfreeware.com) and they were present with that prefix.

This custom, of installing GNU utilities with a g-prefix, isn't just on macOS and Solaris, but also on other UNIX flavours as well.

Re:The Poetics of CLI Command Names by LeoPanthera on Tuesday June 09, 2020 @09:49PM (#23473021)
You used to be able to chose the prefix, until Homebrew removed build options.

(You still can on the BSDs.)