14 ms·
Homebrew's use of analytics still bothers me; specifically, making data public like this. It was supposed to only be used for development efforts, not showing o
by falcolas 9y ago
Homebrew's use of analytics still bothers me; specifically, making data public like this. It was supposed to only be used for development efforts, not showing off top-1000 lists. Also, I guess this following statement is - taking the charitable option - out of date.
> Homebrew's analytics are accessible to Homebrew's current maintainers.
https://github.com/Homebrew/brew/blob/master/docs/Analytics.md#who https://github.com/Homebrew/brew/blob/master/docs/Analytics....
Yeah, I know, my tinfoil hat is quite elaborate.
EDIT: Like I said, my tinfoil hat is quite elaborate; I already have analytics and automated updating turned off. I like to retain some control over what information is reported back to Google or other projects.
That doesn't somehow boost my confidence in Google and volunteer-run open source projects to properly respect the privacy of their users.
- arkadiyt 9y agoReminder, you can opt out of this with: brew analytics off You can check the current status with: brew analytics
- teej 9y agoLet me lend you this handy piece of code, straight from my production codebase, written the day this feature was released. # disable homebrew from tracking metrics # see https://github.com/Homebrew/brew/blob/master/docs/Analytics.md HOMEBREW_NO_ANALYTICS=1
- thesmallestcat 9y agoYou're running Homebrew (and presumably OSX Server, if it still is a thing) in production??
- woodruffw 9y agoHomebrew maintainer here. That language could probably be more precise - only current maintainers have access to detailed analytics (the details being specified on that same page). I wasn't part of the creation of that particular page, but one thing we (the maintainers) commonly find ourselves doing is publicly referencing install statistics as justification for removing an unused formula or taking extra care during a version bump. Having public statistics for the top 1000 most popular packages makes those considerations a little bit more transparent. Edit: I've created a PR to fix the language: https://github.com/Homebrew/brew/pull/3120 https://github.com/Homebrew/brew/pull/3120
- falcolas 9y ago> as justification for removing an unused formula This does not, in my mind, help the case at all. This culture of deletion makes no real sense to me; something not being used for a month or a year doesn't mean it's not being used at all. What's the real cost of just leaving those formula around? A slight problem with it not working immediately when it is used? At least then it can be fixed, instead of seeing the "No formula found" text. The culture of deletion surrounding the long tail of digital artifacts just doesn't make any sense. Yeah, yeah. Get off my lawn, too.
- AlphaSite 9y agomaintain burden. betroth and the fact that git/GitHub really doesn't like huge dirs.
- sillysaurus3 9y agoI've been delighted to install casks using `brew cask install X` where X is some obscure program that I thought brew cask would never have bothered adding. Stuff like that dazzled me about brew cask, so I hope it never goes away even under the guise of maintenance burden. (It's pretty easy to contribute your own formulas, too! The checklist is pretty small.) That said, I've occasionally run into a broken `brew cask install X`, so I get that maintenance is a thing. But in that situation it seems best to let someone else notice that and contribute a patch rather than remove it entirely. I understand that might eventually lead to a large percentage of broken casks though.
- woodruffw 9y agoAs a nit, `brew install` and `brew cask install` use largely different codebases ;) In the best case, the community does pick up the work of patching and maintaining formulae (and casks). However, that's the best case, and low-volume formulae rarely fall into it. In my experience, formulae tend to get abandoned by the upstream that originally submitted them, causing them to eventually break when the system or surrounding dependencies change. One potential solution is to have a chain of custody for formula maintenance, but that hasn't worked so well for MacPorts.
- slagfart 9y agoThere's significant value, when developing a product, in knowing which other products your customers are likely to have, so that you can prioritise your different integrations. Similar data could probably be compiled from Google Trends, but this clean and authoritative view is something that can be trusted, and I think the result makes the open-source ecosystem stronger.
- falcolas 9y agoThat only sets up the value proposition for the maintainers - not for making it public. What value do any of us, not on the Homebrew maintenance team, derive from this list (other than fuel for "X is better than Y" arguments)?
- always_good 9y agoIt's interesting.
- nwatson 9y agoIt informs me of software I didn't know about and yet is popular among presumably mostly developers and power users. I need to know about that.
- stephenr 9y agoThere are literally dozens of "how I setup my machine/tools I use" lists and even setup scripts on GitHub.if you "need" to know what others are doing, refer to those. Or ask. I'll happily tell you my toolset, but I don't use home brew and I wouldn't allow it to send my usage to google even if I did
- marcomonteiro 9y agoThanks for being so open to sharing. Do you have a blog? How do I find your blog? Before you posted this comment how would I even know to look you up. Just because someone on the internet had a particular setup doesn't mean I want to follow it. Or that I have time to track down several people's opinions. Getting install stats directly from the homebrew project, which I know because I use it, is infinitely more useful to me and much more easily discoverable. that's just my opinion though and you're entitled to your own.
- opaque_salmon 9y agoI'm curious why releasing data in this fashion is troubling? It think this kind of public data sharing in an open-source project is good, since it builds transparency. A top-N list seems like a good way to measure the health of the Homebrew ecosystem, similar to other package managers. Without any other identifiable information like email addresses, it seems near impossible to de-anonymize statistical usage from this set.
- falcolas 9y ago> similar to other package managers Interesting; I don't see apt, dpkg, nix, or yum maintainers releasing top lists of packages. Even the package providers rarely provide a "top" list, especially one with compile-time flags. Those flags being provided in this list are very explicit, which could be easily correlated with data provided (or harvested) by other parties. > a good way to measure the health of the Homebrew ecosystem What value does this really provide to the general public, other than a, ahem, "member" measuring contest? You already see this occurring in this very thread - the MySQL vs. PostgreSQL comments. I fully expect a "Node vs. X" one as well.
- jhgorrell 9y agoHelps to find packages which I might have missed from other sources. LWN is good, but doesnt cover everything.
- zanchey 9y agoDebian publishes statistics gathered by the optional "popularity-contest" package at http://popcon.debian.org http://popcon.debian.org I can't remember whether the default is opt-out or in with the current installer.
- stephenr 9y agoIt prompts if you want to install it. It also doesn't sent data to a privacy abusing company like google.
- mikemcquaid 9y ago> volunteer-run open source projects to properly respect the privacy of their users If you don't trust us to respect your privacy why are you trusting us to download and run code from the internet on your machine? We need analytics to effectively run the Homebrew project (as you've noted: we are volunteers). If you no longer trust our project: go use something else.
- falcolas 9y agoIn short, I can verify what's being done on my computer. I can inspect the formulas and verify that what is claimed to be executed is what is actually being executed. I can't on yours (or Google's). EDIT: I'm sorry, was there something factually wrong with this statement to warrant downvoting it into oblivion?
- mikemcquaid 9y agoYou can trivially verify all the information that's sent by us to Google; we have an environment variable to do exactly that.
- fs111 9y agoThere is always macports: https://www.macports.org/ https://www.macports.org/