Hacker News Reader

Comment by dharmab | Hacker News Reader

Notable examples:

- macOS uses BSD-style coreutils while most Linuxes use GNU coreutils. They have different args, output and behavior in many common cases.

- macOS ships with Bash v4. Bash v5 is a common default package on modern Linuxes.

- While the basic user permissions are the same, the OS security model is entirely different. There's no direct equivalent to namespaces in macOS and no direct equivalent to SIP in Linux.

View on HN

MacOS has zsh as a default shell since 2019.

Having `zsh` as a default shell, and having two different versions of `bash` are very different things. That's a bit like saying "macOS ships with IPython as the default Python interactive interpreter" when someone says macOS ships with Python 2.7 when 3.x is available elsewhere.

You are missing the point. I am saying that macos ships with zsh nowadays, having bash 4 installed for legacy compatibility.

Are there any community efforts on solving those issues?

You can download alternative GNU coreutils from Homebrew, but they will need to install under different binary names.

You can download Bash v5 from Homebrew.

In my opinion, Brew solve the first two.

Brew is a pretty bad solution by any metric but especially here. Brew won't replace your coreutils or change your OS's internal tooling.

Thank God it doesn't, what do you want? Subtly breaking everything not written with GNU coreutils in mind?

Reply on news.ycombinator.com