Live data from Hacker News

Homebrew 1.4.0

brew.sh

211–219 of 219 posts

Re: Homebrew 1.4.0

#211

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

And now MikeMcQuaid has actually banned me (presumably from the whole organization) over this.

Mike, I don't know what you think you're doing, but you threatened to ban zenspider simply because they asked to have their issue reopened, and you actually banned me because I pointed out that your behavior was unacceptable. I'd go so far as to say you're actually violating your own Code of Conduct, and if you had any sense whatsoever, you'd immediately stop interacting with the community and appoint someone else to handle all tickets from here on out.

Re: Homebrew 1.4.0

#212
post #194
post #28

Earlier quoted context omitted.

I love that one. I now regularly use "invert a binary tree" as a proxy joke for "let's grill you at a whiteboard with algorithmic puzzles that we never use in practice here but they make a great reason for us to belittle and laugh at you for not being desperate enough to drill these kind of questions for months before coming here"

This is the thing that always confuses me. Google is a company that we all associate with a fairly high quality of technical work, and yet they still appear to use as interview questions what we'd all consider to be really poor proxies for on-the-job performance. I can't seem to reconcile those two things.

That's easy enough: Google is sufficiently big and well known that even if they have an alarmingly high false negative rate, they will never run out applicants, and "weeding out" even a lot of high quality applicants doesn't substantially reduce the average competence of the remaining pool. And the company is big enough that it can absorb the occasional false positive as well, especially when it comes to people who know their algorithms but not, say, how to work on a team effectively.

Re: Homebrew 1.4.0

#213
post #4

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.

Thanks for this comment. I just added my little bit of support, as did a a couple dozen others.

Re: Homebrew 1.4.0

#214
post #117

Earlier quoted context omitted.

BS corporate red tape is a reality, though. So why not offer workarounds that help them give you money?

As mentioned above, offer consulting services and accept corporate purchase orders. Be able to give and receive PO numbers. This is the language the bean counters speak, and sprinkles magic pixie dust on your invoices, ensuring you get paid.

One really big downside to offering this yourself or providing it as a service: contracts. You can try avoid paying a lawyer and use a standard contract. The engineering manager would be cool with that since he just wants to support a project but all bets are off when it hits legal. A big enough company and you can get into a seemingly endless revision back-and-forth that can last weeks. No big deal for them and other big companies they work with since they have salaried lawyers on staff but the cost is something to consider for everyone else.

Re: Homebrew 1.4.0

#215
post #131

Earlier quoted context omitted.

Besides, what does a version number reveal? “Oh, Apple is working on a new OS version!” You don’t say??

Certainly not much if anything at all, but it's mildly interesting to note that it identifies as 10.14 and not, say, 11.0. Anyways there is surely something strange brewing for the next macOS, as Apple has repeatedly noted that "macOS High Sierra will be the last macOS release to support 32-bit apps without compromise ", without specifying what kind of "compromise" might come up (see https://developer.apple.com/news/…

I think you might be reading that wrong - should be "Without compromise, macOS will discontinue support for 32-bit apps". The only compromise should be not upgrading to 10.14 and staying on 10.13.

Re: Homebrew 1.4.0

#216

Earlier quoted context omitted.

As mentioned above, offer consulting services and accept corporate purchase orders. Be able to give and receive PO numbers. This is the language the bean counters speak, and sprinkles magic pixie dust on your invoices, ensuring you get paid.

One really big downside to offering this yourself or providing it as a service: contracts. You can try avoid paying a lawyer and use a standard contract. The engineering manager would be cool with that since he just wants to support a project but all bets are off when it hits legal. A big enough company and you can get into a seemingly endless revision back-and-forth that can last weeks. No big deal for them and othe…

Hiring a lawyer is important if you are going to be contracting with a large enough company though. The money you save and the time you spend as a result of having a competent lawyer draft, negotiate, and proof your contracts pays for itself in the long run when, inevitably, something goes wrong on a project.

Re: Homebrew 1.4.0

#217
post #199

Earlier quoted context omitted.

Ask for permission - opt-in not opt-out. The current behaviour isn't sufficient for the new GDPR requirements coming in May. Contributors and any relevant companies (or their subsidiaries) in the EU could be liable.

GDPR covers personal data, not anonymous unidentifiable stats.

You are incorrect - this is personal data and does fall under the extremely wide scope of GDPR, which is simply "processing".

Under the current data protection laws, as long as it isn't personally identifying, it would fall out of scope. Under GDPR, it is in-scope, and explicit opt-in consent is required for both collection and for the things you want to use the data for.

Requiring opt-in to use the software is also not permissible.

GDPR is a bit of a beast.

Re: Homebrew 1.4.0

#218
post #131

Earlier quoted context omitted.

Certainly not much if anything at all, but it's mildly interesting to note that it identifies as 10.14 and not, say, 11.0. Anyways there is surely something strange brewing for the next macOS, as Apple has repeatedly noted that "macOS High Sierra will be the last macOS release to support 32-bit apps without compromise ", without specifying what kind of "compromise" might come up (see https://developer.apple.com/news/…

I think you might be reading that wrong - should be "Without compromise, macOS will discontinue support for 32-bit apps". The only compromise should be not upgrading to 10.14 and staying on 10.13.

Maybe. It's an odd phrasing. Why not just say "will not run"? How do you run 32bit apps "WITH compromise"? In a VM window?

Re: Homebrew 1.4.0

#219

Earlier quoted context omitted.

Why are they discouraged to run Homebrew?

Security no doubt. Homebrew security is good enough for you and me but not good enough if you're working on Apple software.

> but not good enough if you're working on Apple software

Why not?

Post reply on HN