> he couldn't remember some useless piece of easily-googleable (ha) CS trivia on the spot.
Or that's what he claimed.
> Even though they all run it internally.
That's what he claimed as well. But never heard of Homebrew while I was at Google, though I had a Macbook for 5+ years. (Well I can't definitely say my Macbook never ran Homebrew - after all, when you are in Google, all such things are handled by dedicated teams. But I can definitely tell that this "scandal" was the first time I heard about Homebrew.)
Not trying to take him down - I'm now in a different company and use Homebrew quite happily, but it's simply not true that it was widely used inside Google.
Google is a Linux shop. Most Googlers don't do any development on Mac (unless they're specifically working on something that runs on Mac, like maybe Chrome). Each one has a linux desktop (or at least that was the case while I was there), and all the heavy work is done "in the cloud" anyway.
Besides iOS developers and maybe open source developers, people don't and aren't allowed to have code on their laptops at Google. You have to ssh into your desktop so presumably there's no reason to have Homebrew unless you're doing personal stuff.
Or that's what he claimed.
> Even though they all run it internally.
That's what he claimed as well. But never heard of Homebrew while I was at Google, though I had a Macbook for 5+ years. (Well I can't definitely say my Macbook never ran Homebrew - after all, when you are in Google, all such things are handled by dedicated teams. But I can definitely tell that this "scandal" was the first time I heard about Homebrew.)
Not trying to take him down - I'm now in a different company and use Homebrew quite happily, but it's simply not true that it was widely used inside Google.