Live data from Hacker News

Homebrew 1.0.0

brew.sh

21–30 of 255 posts

Re: Homebrew 1.0.0

#21
post #20
post #19

I'm excited about Homebrew potentially coming to Linux. When I first started using OS X more regularly, I was surprised by how better an experience OS X + Homebrew is compared to Ubuntu/Debian repositories + PPAs/third-party repositories.

Isn't it there already? https://github.com/Linuxbrew/brew

I don't know much about Linuxbrew, but that looks like a fork, not Homebrew officially supporting Linux.

Re: Homebrew 1.0.0

#22
post #8

Throwback to that one time Google wouldn't hire @mxcl. ;) https://twitter.com/mxcl/status/608682016205344768 Well done Mike and contributors! It's a great piece of work.

It's hard for me to understand the issue with this. Google didn't hire the guy who wrote software that had a big impact on the community. Does it mean Google misses good engineers because of their less-than-ideal interview process, or simply Google hires only people who are a good fit for their organisation?

Writing the overly bitter tweet surely won't help with improving hiring points. Seems highly unprofessional and childish.

Re: Homebrew 1.0.0

#24

There has been a lot of talk in HN comments recently about Homebrew installing to `/usr/local`. With macOS Sierra, the user can no longer write to this folder without specifically owning it. Is there a security risk here and if so, whats the best workaround?

Newer versions install in `/usr/local/Homebrew`, older versions "migrate" there: http://apple.stackexchange.com/questions/253404/how-does-hom...

I have a hard time understanding the "migration", even after reading all the related issues. Homebrew still writes into /usr/local/bin and /usr/local/Cellar, nothing different from the past. What exactly changes?

Re: Homebrew 1.0.0

#25

Earlier quoted context omitted.

Except for loading the Ruby VM. Takes way too long.

Which is why for certain things like `brew --prefix` we now do it purely in Bash rather than using Ruby ;)

Why would bash be faster ? Would not you essentially call the same C lib stuff anyway ?

Re: Homebrew 1.0.0

#27
post #8

Throwback to that one time Google wouldn't hire @mxcl. ;) https://twitter.com/mxcl/status/608682016205344768 Well done Mike and contributors! It's a great piece of work.

It's hard for me to understand the issue with this. Google didn't hire the guy who wrote software that had a big impact on the community. Does it mean Google misses good engineers because of their less-than-ideal interview process, or simply Google hires only people who are a good fit for their organisation? Writing the overly bitter tweet surely won't help with improving hiring points. Seems highly unprofessional an…

Well, he's at Apple now in charge of the Swift Package Manager, so I think he did okay.

Re: Homebrew 1.0.0

#28
post #21
post #20

Earlier quoted context omitted.

Isn't it there already? https://github.com/Linuxbrew/brew

I don't know much about Linuxbrew, but that looks like a fork, not Homebrew officially supporting Linux.

[deleted]

Re: Homebrew 1.0.0

#29
post #25

Earlier quoted context omitted.

Which is why for certain things like `brew --prefix` we now do it purely in Bash rather than using Ruby ;)

Why would bash be faster ? Would not you essentially call the same C lib stuff anyway ?

It would at least save the process-start overhead, plus loading the ruby vm and modules/gems.

Re: Homebrew 1.0.0

#30
post #8

Throwback to that one time Google wouldn't hire @mxcl. ;) https://twitter.com/mxcl/status/608682016205344768 Well done Mike and contributors! It's a great piece of work.

It's hard for me to understand the issue with this. Google didn't hire the guy who wrote software that had a big impact on the community. Does it mean Google misses good engineers because of their less-than-ideal interview process, or simply Google hires only people who are a good fit for their organisation? Writing the overly bitter tweet surely won't help with improving hiring points. Seems highly unprofessional an…

I will just assert that at Googe scale (some 20000-30000 engineers from a quick search), "good fit" isn't really a thing. Now, it doesn't mean they might not be hiring a certain mono-culture type of programmers, but that might not be a "fit" issue (Disclaimer: I do think "good fit" is vaguely defined)

And I'd love to see a counter assertion/argument.

Post reply on HN