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.
If there were Enterprise Homebrew that did nothing different but sent me an invoice every month, I could effortlessly expense it for $100s/month.
Homebrew 1.4.0
91–100 of 219 posts
Re: Homebrew 1.4.0
#92How does one upgrade?
brew updateRe: Homebrew 1.4.0
#93The 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.
Basically anyone who does any kind of work with code on a Mac is pretty likely to be using Homebrew for something or another.
Re: Homebrew 1.4.0
#94does homebrew still* use Github as the store for all packages? Just curious, that always seemed like a strange scenario. * or am I wrong that it ever did?
Re: Homebrew 1.4.0
#95Earlier quoted context omitted.
One of my less-favorite things is how many people always pop up to defend the Google approach and argue that if he couldn't pass such an interview he must by definition not be qualified.
I can count the number of times I've needed to implement any binary tree algorithms on one hand. And they've all been either homework when I was in undergrad, or job interviews. That said, I'm pretty sure that interview questions like these are not about whether or not someone is qualified to do the job they're actually doing, and 100% about companies trying to come up with a standardized, one size fits all tech inte…
The only standardization is the thud of hitting the floor due to all participants expending the least possible effort. Like a team building trust fall where everyone is too busy checking Messenger to be bothered to extend their arms.
The shared failure of institutionalized apathy.
Re: Homebrew 1.4.0
#96Earlier quoted context omitted.
I meant, what do you prefer about one vs the other
I switched to Brew because I got tired of recompiling from source for every update with MacPorts. As an end-user I don't see the benefit of repeating the same thing N times for N clients versus doing it once, centrally. Every time "boost" updates, you're stuck recompiling half your ports for the next 20 minutes to use the new library. With Brew, you wait a minute for the new packages to download, and you're done.
Re: Homebrew 1.4.0
#97Does anyone use MacPorts/Fink anymore? What are the use cases for them?
- 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.
Re: Homebrew 1.4.0
#98Does anyone use MacPorts/Fink anymore? What are the use cases for them?
Not that we have any problems with MacPorts really.
I too am curious about qualitative differences between the two.
Re: Homebrew 1.4.0
#99Earlier quoted context omitted.
Reminds me of one of patio11's posts somewhere. I don't remember which one, but the gist is that big companies basically can't donate to tipjars, patreons, etc. But if you make it a product with an enterprise option for support or something, they'll gladly pay tens of thousands a month.
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.
Re: Homebrew 1.4.0
#100Earlier quoted context omitted.
For a lot of the people Google needs to hire to write Google-scale code, maybe "can identify things that people want and need and actually implement them"" isn't a particularly useful skillset _to Google_, but the skill set of "ingrained knowledge of data structures useful to writing scalable, low-level code" is. I do agree that the "make things people want" is a very useful/desirable skillset for a vast array of non…
Sure, that's what I was trying to convey in the paragraph after D. That said, I think that even for a company Google's size, having those different skill sets will be useful as your business ages. Google will probably always need a number of people that have memorized every data structure known to humanity, but they would probably be better set up to avoid stagnation and continue in a position of market dominance int…
Yep, agreed! But since there's probably some overlap in that candidate skillset Venn diagram, maybe they're getting the people that can do both, and the data-structure skillset's the one that's possible to consistently interview for.