Live data from Hacker News

Homebrew 1.0.0

brew.sh

111–120 of 255 posts

Re: Homebrew 1.0.0

#111
post #29

Earlier quoted context omitted.

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

Exactly. For a simple string comparison Bash is far faster (although Homebrew doesn't use require any gems, just FYI).

Good to know, so did the speedup come mostly from not spinning-up the Ruby VM?

Re: Homebrew 1.0.0

#112
Thank you Homebrew!

As corny as this may sound. I rely on Homebrew to get my unix experience on OS X and not have to compile everything myself. Saves me time and is one less wrench in my development process.

Re: Homebrew 1.0.0

#113

Be aware of "update bug" If Homebrew was updated on Aug 10-11th 2016 and brew update always says "Already up-to-date". you need to run: ``` cd "$(brew --repo)" && git fetch && git reset --hard origin/master && brew update ``` I had to.

I also had to do this. Keep in mind that ```brew update``` might take a while to output anything when you do this (it did for me), and then it will ask you to wait while it migrates to a new directory.

Re: Homebrew 1.0.0

#114
post #107
post #54

I had uninstalled homebrew this week because it stopped functioning. Out of nowhere, I started getting a ruby error related to a particular package and every CLI call would fail because of it. As someone who works with Go, it's sad to see an error bubbling up and not being gracefully handled.

I had errors with Homebrew and Go this week. In both cases, it was an issue with Websense (also known as Forcepoint). Might your issue be related to that?

Brew claimed it couldn't find the downcase for another package, not Go.

Re: Homebrew 1.0.0

#115
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…

Does it mean Google misses good engineers because of their less-than-ideal interview process

Google intentionally prefers false negatives to false positives.

Re: Homebrew 1.0.0

#116
I have a stupid question. Is there a dogmatic way of listing installed things and sharing that with other brew?

For example, I now list with brew list into a file and edit the file so that whole list is a big brew install. That way if I reinstall OS or go to another I can have same things.

Re: Homebrew 1.0.0

#117
post #51

Earlier quoted context omitted.

I'm wondering if Macs would be as successful with developers without homebrew.

Mac OS X came out in 2001, and there was a lot of immediate adoption by people using emacs and bash: It became the largest consumer distro of a Unix-based system overnight. (look for all the old articles about how to upgrade from tcsh to bash). Homebrew was successful because there were developers who wanted it. Is the Mac more successful as a developer platform because of it? Possibly.

It's fun to read all of this. I re-read John Siracusa reviews and some old blogs and yes, until Snow Leopard OSX was THE cool hackers' OS. And when Apple didn't invest in power users anymore, individuals took over.

Re: Homebrew 1.0.0

#118
post #55

"brew update Error: /usr/local is not writable. You should change the ownership and permissions of /usr/local back to your user account: sudo chown -R $(whoami) /usr/local . . . ==> Migrating HOMEBREW_REPOSITORY (please wait)... ==> Migrated HOMEBREW_REPOSITORY to /usr/local/Homebrew! Homebrew no longer needs to have ownership of /usr/local. If you wish you can return /usr/local to its default ownership with: sudo ch…

I see no problem in this. We need writing permissions to /usr/local to finish our migration (as we always did). Once you finish the migration we (hopefully) never write directly to /usr/local again.

Sorry, I probably failed to notice the "Thanks Homebrew team. <3" part first time round.

Re: Homebrew 1.0.0

#119

I have a stupid question. Is there a dogmatic way of listing installed things and sharing that with other brew? For example, I now list with brew list into a file and edit the file so that whole list is a big brew install. That way if I reinstall OS or go to another I can have same things.

Don't know if there is but that's a great idea. I always had a pain of brew installing on new systems. Especially when you want to lock versions of some things (MySQL etc).

Re: Homebrew 1.0.0

#120

I have a stupid question. Is there a dogmatic way of listing installed things and sharing that with other brew? For example, I now list with brew list into a file and edit the file so that whole list is a big brew install. That way if I reinstall OS or go to another I can have same things.

Not sure if that's what you wanna do but you could do :

"ls /usr/local/Cellar/ | cat >> myInstall.txt"

Post reply on HN