Meanwhile, my local Gitlab install just hums along no issues.
Days without GitHub incidents
71–80 of 178 posts
Re: Days without GitHub incidents
#72Earlier quoted context omitted.
It's not great. Just talked to a hubber last week. They said everyone inside feels pretty dejected right now, and these posts don't help. I feel for them -- with AI coders submitting 25 PRs within an hour of an issue being filed, GitHub bears the brunt of that along with the maintainers. That's a lot of work that gets done with each PR. But they need to make some changes quickly.
But the amount of compute needed to serve is not very high. It's all text. The amount of bandwidth and compute needed to serve a Netflix or YouTube is far far harder and they managed just fine.
They should migrate to AWS.
Its webscale
Re: Days without GitHub incidents
#73Earlier quoted context omitted.
Executives have made a choice to not pay for top talent at Microsoft Azure and Github.
Would you consider telling this to the people working at GitHub directly? I’m sure they’d appreciate your evaluation of their skills and talent.
yes I would tell them "you're underpaid, if you can, come to a company that appreciates your talents more".
Re: Days without GitHub incidents
#74Lots of apologia for Github here. Aside from the fact that defending a billion-dollar company is a bit strange; especially one that is steward to the the overwhelming majority of open-source software. Maybe that's good-will doing the work? For me it's always been a sour pill to swallow that I have to buy in to a large companies internal politics and practices in order to work on projects I love. I don't feel like I o…
I'm surprised at how little the perception of GitHub changed post-acquisition. Coupled with WSL, it almost balanced things for a lot of people and put Microsoft back in the "benefit of the doubt" column. This is undoing a lot of that, on top of the operational costs. Suddenly the bad press is more noticeable and harder to ignore.
As far as I'm concerned, any benefit of the doubt I might have had for Microsoft is gone after this debaucle: https://news.ycombinator.com/item?id=47989883
Re: Days without GitHub incidents
#75Earlier quoted context omitted.
The whole "anyone can submit a PR" thing has been a UX issue from day one. That probably needs to go away, and I doubt anyone would really miss it. Where Github could help is by providing a means to build trust that doesn't involve random unknown people slinging code at projects.
Any sort of trust requirement would break the entire model and cause some serious inequality. How would a random kid in a 3rd world country ever get noticed enough to enter a trust circle, for example?
That's a hard problem! I don't know. But when we select colleagues we build trust before we let them in the building by interviewing them, looking at their work, checking their references. So maybe there's some sort of analogous process that isn't just "here's a big PR, look at it" that would be useful? If there was such a process, maybe that kid could go through it and become trusted.
EDIT: from Github's selfish perspective, this would gatekeep their CI load. I assume (I have no idea, it's just a guess) that mostly serving source code and handling commits is not primarily the scale problem. Instead (again just guessing) probably the vast majority of the compute load due to PRs is running all the CI checks. Nontrivial projects can spawn a hell of a lot of compute per PR, and on every subsequent commit pushed while the PR is open.
Re: Days without GitHub incidents
#76Should be 0 today AFAIK
EDIT: I’m a moron, lol.
Re: Days without GitHub incidents
#77Should be 0 today AFAIK EDIT: I’m a moron, lol.
it already is. re-read?
Re: Days without GitHub incidents
#78Re: Days without GitHub incidents
#79Earlier quoted context omitted.
I wouldn't feel too bad for them with their top-of-market comp and valuable RSU packages.
I don't believe they pay top of market, but even if they did, it's possible to make a lot of money and still feel bad when you have a sense of ownership and responsibility to the users of your service.
You missed my point.
Re: Days without GitHub incidents
#80That purple to blue gradient is the emdash of css.