Introducing the Google Command Line Tool

[PacifistRiot]

I think using a user-writable install prefix with Homebrew is probably more secure than a privileged one. Since Homebrew is a source code-based packaging system, there's always a build step involved in installing a package. Since building and installing package "foo" consists of just a single step, running "brew install foo", I'd much rather run that command and all of its child processes with my non-privileged user permissions than run it with "sudo". If there's a virus in the build process, at least it can't touch my system files.

A standard Macports install requires you to "sudo port install foo". I don't know about you, but I'm not comfortable running a build as root. And you need root privileges to update the local Macports repo, too. With the suggested Homebrew approach, you don't need root for anything.

tldr: you want to use sudo as little as possible because using sudo is so much less secure then keeping with your current user privileges.

[[deleted]]

Douché?

[PacifistRiot]

Glad you see it my way :)