News for hackers. Stuff that matters.
Re:OS X Command Line Utilities by jmount on Sunday August 30, 2015 @11:35AM (#10143566)
Without something like Homebrew you don't get any current Unix tools (OSX shell is way out of date) or anyway to systematically update them. This is a big benefit that far outweighs any perceived benefit dropping bundles into /Applications. And you get some attempt at installation of dependencies.
Re:OS X Command Line Utilities by pjmlp on Sunday August 30, 2015 @12:13PM (#10143676)
What are current UNIX tools? OS X supports what is expected from a POSIX compliant OS.

I guess you mean BSD and GNU extensions to POSIX.

Re:OS X Command Line Utilities by hk__2 on Sunday August 30, 2015 @01:18PM (#10143885)
OS X ships outdated versions of Bash and Git for example. The 10.10.5 version ships Bash 3.2 and Git 2.3, while Homebrew gives you Bash 4.3+ and git 2.5+.
Re:OS X Command Line Utilities by pjmlp on Sunday August 30, 2015 @03:32PM (#10144252)
This is the usual mistake young generations do in regard to UNIX, neither bash nor Git are part of UNIX standard.

POSIX IEEE Std 1003.1, 2013 Edition defines sh as the shell.

There is no git in POSIX IEEE Std 1003.1, 2013 Edition.

Re:OS X Command Line Utilities by eropple on Sunday August 30, 2015 @04:57PM (#10144471)
Virtually every person who uses any modern Linux or OS X system expects bash to be installed and in the modern vernacular it can be completely and safely considered, in informal discussion, to be part of relevant Unixes. You knew exactly what he meant, but for some reason (and I won't speculate but it isn't a good look on you) you decided to be pedantic for the sake of being pedantic. You're not being helpful to anyone or anything and should stop, and you know it.
Re:OS X Command Line Utilities by stephenr on Monday August 31, 2015 @02:07AM (#10145647)
The majority of people who use Bash on OS X will not be using advanced features.

The people that are likely to use advanced features would also hopefully be aware of Bash's fragility/compatibility issues between minor versions, and thus wouldn't rely on it for anything like shell scripts.

So we're left with people who want to use advanced features and are doing so purely on machines they control.. So what stops them from either compiling their own bash, or using one of the third party package managers to install it?

Re:OS X Command Line Utilities by eropple on Monday August 31, 2015 @02:11AM (#10145660)
It shouldn't be the job of a third-party package manager to do this. I want my vendors to stay up to date not just for feature purposes, but for security ones, too. (Remember how long it took Apple to get a Shellshock patch out there?)

But I have less of an interest in that than in discouraging jerkish pedantry.

Re:OS X Command Line Utilities by jmount on Sunday August 30, 2015 @10:42PM (#10145184)
A Unix derived operating system with a package manager (BSD Ports, Linux debian/apt or rpm) is way more powerful than one without. Half the time I am installing stuff I don't particularly like or want- but that is necessary to complete a project.
Re:OS X Command Line Utilities by odbol on Tuesday September 01, 2015 @08:18PM (#10156695)
hahahaha I see you've never tried to use rsync on a Mac. Some (documented) command line options just DON'T work. They're in the manpage, but they don't do anything. There's lots of other little gotchas in other utils as well, especially when coming from Linux.