The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage. I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.
Up to $304 already, good job guys!
Homebrew 1.4.0
161–170 of 219 posts
Re: Homebrew 1.4.0
#162Earlier quoted context omitted.
Saying "the error message is terrible" isn't particularly rude to begin with. And if you're having a one-on-one conversation with someone, saying "I think you're rude so I'm not going to answer your question" is one thing, but in a public forum, saying "You raise a valid question but I don't like how you phrased something so I'm going to explicitly refuse to answer the question, then lock the PR so nobody else can as…
It's not much of an argument to say "well, it's not really that rude". Is it generous and gracious to communicate with people despite their rudeness? Sure. But should it an obligation, particularly for an open-source maintainer? Absolutely not. Nor do I buy the "public forum" argument. You direct your writing to the audience you have (i.e., the person that asked you a question rudely), not an imagined audience that m…
Saying the error message was terrible is barely rude at all. The only real problem with it is it's non-specific. And the poster edited their message to change the wording immediately anyway, the maintainer was only annoyed because GitHub emailed him the original contents of the comment.
So the maintainer took an extremely minor just-barely-qualifies-as-a slight and decided to react about as bad as you possibly can. It's awful.
And I'm not projecting either. zenspider had a legitimate complaint and a real question, both of which I care about. The complaint still hasn't been addressed, and the only way I was able to get an answer to the question was to ask here on HN. But that answer isn't visible to anyone else who looks at that PR (i.e. anyone who sees the changelog entry and wants to know why the CLT are now required), which I guarantee you is a nonzero number of people.
Re: Homebrew 1.4.0
#163> Homebrew requires the CLT on all but the latest version of macOS (to avoid copious workarounds in formulae) Why? What are these workarounds? The linked PR didn't explain, and as someone who's still got one machine on 10.12 I'd really rather not have to keep CLT installed as well. Edit: Wow, the maintainer on that PR is a real jerk. He refused to answer a legitimate question (and locked the PR at the same time) beca…
Homebrew is an awesome, super useful piece of software that people put in tonnes of effort to maintain, for free. Your complaint was indeed worded rudely. Also, re: the “why” behind this commit, “to avoid copious workarounds in formulae” is already a pretty good description, I can see why he didn’t feel the need to elaborate. Remember that maintainers of projects like Homebrew have to deal with an endless stream of c…
It wasn't my complaint.
And no, that's not a good description, because it gives me literally zero information to go on in order to find out what the workarounds were, how many formula actually needed them, and what the problems were that necessitated this.
> Remember that maintainers of projects like Homebrew have to deal with an endless stream of complaints and feature requests
Yeah, that's what happens with popular open source projects. Good projects are able to handle this in a way that doesn't alienate the community or future contributors. The fact that MikeMcQuaid is doing this for free does not remove the obligations he has to the community.
Re: Homebrew 1.4.0
#164Earlier quoted context omitted.
Yes, exactly! I face this with my government clients. They spend very little time thinking of the actual amount (even if it's $30k), and more time about "how are we going to purchase this??" Tip Jars aren't an effective way to get money for this stuff, at least if you want money from companies. It's good for "aw this library helped me, let me throw in $5" from individuals.
Tip jars and pay what you can are effective. Bs corporate red tape is the problem
What makes it BS? Can you come up with a better way to manage giving access to a bank account with hundreds of millions of dollars to a thousand people?
Re: Homebrew 1.4.0
#165The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage. I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.
If you look into the OS version analytics, there are 397 events registered from "macOS (10.14)". That's the next version of macOS :) https://brew.sh/analytics/os-version/
Perhaps someone deliberately messing with their version string, e.g. testing the software to make sure it handles "unknown" or "future" release cases properly?
Re: Homebrew 1.4.0
#166Earlier quoted context omitted.
what do you want them to do?
At first install, prompt the user to opt-in? Occasionally re-prompt a user, say, once per year to choose to opt-out if they’re opted in, just to check they’re still cool with it and haven’t forgotten and/or changed their mind on how comfortable they are with the practice? People’s opinions on that sort of thing don’t always remain static.
Opt-in is a decent enough method. But "Occasionally re-prompt a user" is a horrible idea, in my opinion. From a user perspective, that's kind of like the software forgetting the options you set. The very first time that something re-prompted me about something I had already opted-in to or out of, I would feel intense rage that it's asking me something that it had already asked me.
Re: Homebrew 1.4.0
#167Does anyone use MacPorts/Fink anymore? What are the use cases for them?
MacPorts user here. Uses case are the same, but: - MacPorts does not track you by default with Google analytics. - MacPorts lives by default in a self-contained directory tree. - MacPorts tends to be more stable than Homebrew, but that’s just my personal experience. - I didn’t like the slogans Homebrew used for years, implying MacPorts wasn’t good quality.
Does MacPorts have anything like Homebrew Cask? I know it's technically a plugin/addon, but it owes its existence to the Homebrew tooling and ecosystem it's on top of.
The ability to very easily install full GUI apps, or closed-source ones, is absolutely indispensable for automatically configuring Macs in many large environments, especially those (like a former one of mine) that heavily used Puppet for provisioning.
If MacPorts is lacking in that "umbrella package manager" functionality, I'd be stuck using both it and cask if I switched (and, given my positive experiences with Homebrew core and cask, I have no plans to).
Re: Homebrew 1.4.0
#168Does anyone use MacPorts/Fink anymore? What are the use cases for them?
I like MacPorts over Homebrew because MacPorts lives in its own directory. Homebrew can hose your system binaries and that was enough for me to never use it.
Homebrew, like, for example, CPAN, runs reasonably arbitrary code at package-install time. Much of it is sandboxed, or reviewed by the maintainers, but scripts/configure programs/etc. can spray files, or remove files, anywhere they want on your system. The same is true with ill-behaved "configure; make; make install" deployment systems.
This is contrasted with something like dnf/yum, which has registries of assets that are supposed to be installed. I'm not positive, but I suspect something like that would be a way higher maintenance burden for OSX (for maintainers of the package management system and packagers themselves, many of whom have shown little to no interest in packaging for OSX, hence Homebrew's patch system).
It also lives primarily in its own directory, unless you're installing casks (which usually "do exactly what the installer would do if I downloaded and installed it myself") or packages with special cases that manage external-to-homebrew things. For packagers, the API for "use Homebrew-managed/blessed directories for e.g. --prefix configure arguments" is pretty good, but people (and bad, old build scripts) can and do still mess around outside of where they're supposed to. "Hosing your system binaries" is a pretty darn rare occurrence unless you're explicitly configuring brew to put things where it wouldn't normally.
Edit: plurals are hard.
Re: Homebrew 1.4.0
#169The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage. I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.
https://www.patreon.com/homebrew
It's $312 a month now, but that's still super now. We should at least get them to where they can afford a few beers with the monthly groceries.
Re: Homebrew 1.4.0
#170The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage. I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.
[deleted]