Live data from Hacker News

Homebrew 1.0.0

brew.sh

211–220 of 255 posts

Re: Homebrew 1.0.0

#211
post #71
post #40

Earlier quoted context omitted.

It's for this very reason that I'm still one of those old-school guys who still uses MacPorts. I was horrified to see this, and in my brief time using it, it actually caused me real problems, so I went back.

I switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720…

was it that hard to just, you know, type "brew analytics off"? Or was there more to that decision?

Re: Homebrew 1.0.0

#212

Earlier quoted context omitted.

Postgres.app[1] would make your life even easier. :) [1]: http://postgresapp.com/

It's a convenient app but I'm very conscious of menu bar real estate, and mostly don't use it for the reason of adding an icon where the only interaction is launching / quitting it. I wish we had a better GUI for managing a user's daemons on OS X.

It seems like there could be territory here for a menu bar app that hooks into homebrew-services [1]. It'd still take some menu bar room, but it could have one dropdown for a whole variety of services in an integrated way.

[1]: https://github.com/Homebrew/homebrew-services

Re: Homebrew 1.0.0

#213

Homebrew used to be my go-to tool for installing packages... But now, with the new Docker for macOS, I never need home-brew anymore. It is especially helpful when you need to run 2 different versions of an app (like elastic search) for different projects. I can't see myself returning to Homebrew now. That is just not the way to do things anymore.

Apples and oranges. I brew install git, Emacs, jq, and other dev tools. Packaging stuff in Docker is fine, but first you have to create or fetch something to package.

Re: Homebrew 1.0.0

#214
post #211
post #71

Earlier quoted context omitted.

I switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720…

was it that hard to just, you know, type "brew analytics off"? Or was there more to that decision?

I've found that a lot of people here in HN and Reddit are really passionate about not being tracked, so even if it was as easy as one command, the fact that Homebrew did it at all is enough to make some people not want to use it.

Nothing wrong with that viewpoint, but I just disabled it and moved on to enjoying pretty good software.

Re: Homebrew 1.0.0

#215
post #211
post #71

Earlier quoted context omitted.

I switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720…

was it that hard to just, you know, type "brew analytics off"? Or was there more to that decision?

Privacy violations and user tracking should always be opt-in not opt-out. If nobody opts in, one should rationalize why users may not want to be tracked or have their privacy violated and question whether making it opt-out is a good decision and respectful of their users.

Re: Homebrew 1.0.0

#216

Thank you guys for making my life as a software dev and end user infinitely easier. - brew install postgresql - brew install mpv The list goes on and on and on. You rock!

Postgres.app[1] would make your life even easier. :) [1]: http://postgresapp.com/

And you can do `brew cask install postgres`.

Re: Homebrew 1.0.0

#217
post #211
post #71

Earlier quoted context omitted.

I switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720…

was it that hard to just, you know, type "brew analytics off"? Or was there more to that decision?

Most people, myself included, never even heard about this before this point, because it's never mentioned as part of the installation or usage process and is opt-out—if you know it exists and that you might want to opt out in the first place.

Re: Homebrew 1.0.0

#218
As a side note, Ansible users might be interested in the roles I've been putting together for a bunch of the apps I regularly use [1].

You can kinda use homebrew-bundle in place of some of this stuff, but even then there's random installs that need extra configuration or general mucking about with that homebrew-bundle doesn't give a good way to encapsulate (for example, see the duckdns-updater repo and the template it uses [2]).

[1]: http://galaxy.ansible.com/icopp/ [2]: https://github.com/icopp/ansible-duckdns-updater

Re: Homebrew 1.0.0

#219

Earlier quoted context omitted.

My understanding is he just doesn't really know how to work in a big company.

Meh. I know "how to work in a big company" and choose not to. Talented people will always do whatever they want.

You choose not to, but you could if you wanted to, right? He apparently wanted to, otherwise he wouldn't have gone to Apple in the first place, but he just doesn't know how to work in a corporate environment. In fact, he says as much in this tweet: https://twitter.com/mxcl/status/773574683518119936

Re: Homebrew 1.0.0

#220
post #211

Earlier quoted context omitted.

was it that hard to just, you know, type "brew analytics off"? Or was there more to that decision?

I've found that a lot of people here in HN and Reddit are really passionate about not being tracked, so even if it was as easy as one command, the fact that Homebrew did it at all is enough to make some people not want to use it. Nothing wrong with that viewpoint, but I just disabled it and moved on to enjoying pretty good software.

It has nothing to do with how easy or hard it is to disable. The problem is that it doesn't ask first, or even tell you what it's doing. OK, now that I know about it, I can turn it off, but how do I know they won't do something similarly ugly in a future version?
Post reply on HN