Re:Brew commands send data to Google Analytics
by JakeTheAndroid on Friday November 25, 2016 @10:44PM
(#13041614)
That's a bit extreme. A compiler sending your codebase has potential IP implications. Sending your brew commands back to brew is much different.
What commands do you run in brew that isn't specific to brew? Whereas, compiling code is a very specific-to-you scenario. If brew fails, it's likely to be caused by brew itself or a package that is part of the repository. If you your compiler runs into an issue, it's not inherent to the compiler necessarily. I'm not a fan of brew at all, and I can't really find the malice here. Either opt out, stop using brew, or accept it. Why are you on OSX if you care that much about your package manager anyways? Ive worked at many companies, and any that let you choose a MacBook will let you opt for a Linux laptop instead (YMMV I guess).
No, we don't know. This article wouldn't have hit the front page if it wasn't subtle and user-hostile by default (opt-out).
>Data is being sent to Google everytime you do almost anything in almost all websites, using the same technology. So what?
Brew is not a website, it's a CLI tool. People expect this behavior of websites, not of sysadmin tools. How would you feel if you found out your compiler shipped off a copy of your code to a remote server each time you encountered a compiler error "to improve the compiler" and you had to opt out of this behavior?
>Some of the times it's to make the product better, or better targeted. Some other times it's just for spying on the users.
It's always spying, regardless of the motivation.
>How do we expect open source to become better if everyone is being a crybaby because brew got a history of how often they do brew update?
Somehow open source has functioned all of these years without silently harvesting users' usage data. I don't know how new you are to open source, but this is definitely not the way you do QA for an open source project.