4 ms·
Just a minor nitpick, macOS has true bash. It just doesn't have the GNU coreutils, instead it uses the BSD-based equivalents. And yeah, they suck a lot[1], but
by leonidasv 6y ago
Just a minor nitpick, macOS has true bash. It just doesn't have the GNU coreutils, instead it uses the BSD-based equivalents.
And yeah, they suck a lot[1], but there's a way to fix if you use Homebrew: https://stackoverflow.com/a/57973942/8280773 https://stackoverflow.com/a/57973942/8280773
[1] Performance-wise and also when you take into account that most shell scripts/tutorials on the internet are written with a GNU userland in mind.
- Steltek 6y agomacOS has a 12+ year old bash. Also, even with Homebrew patching up Apple's neglect, coreutils behaves differently under a Darwin kernel than Linux. A repeat source of aggravation for myself is the behavior of 'ps'.
- llimllib 6y agothat's not due to the kernel, that's because it's bsd ps instead of gnu ps. sed is the one that gives me the most irritation, there's basically no way to write useful cross-OS sed scripts.
- svachalek 6y agoAs I remember it, this is the whole reason OS X became the de facto standard for developers in the first place, consumer-grade windowing and device drivers coupled with a familiar development environment. zsh has replaced bash as the default shell, btw.