Earlier quoted context omitted.
You don’t know that it was “their mistake.” Unless you’ve personally successfully scaled a suite of nontrivial services equivalent to GitHub’s to accommodate an unexpected 14x increase in traffic, you respectfully have no basis for such an assertion.
Yeah, they should be testing for that, right? I think there's a lot of people reading comments like yours and thinking, is this person a paid shill or what? The earn bucket loads of money, they should be planning for exactly that. And testing for it via load testing every day. Perhaps you've forgotten the days of GitHub presenting themselves of software engineering thought leaders.
Days without GitHub incidents
91–100 of 178 posts
Re: Days without GitHub incidents
#92Earlier 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.
Also, respectfully, you have no idea what you're talking about. "Just text" doesn't make it easy to solve. GitHub Actions aren't just text and take a lot of compute.
Re: Days without GitHub incidents
#93My free, open-source, bare-bones, caching-free, dependency-free, authentication- and authorization-free pure PHP raw Git viewer. I developed it because GitList blew out my shared host's drive space and memory (due to a caching bug) and to consolidate my GitHub, BitBucket, and GitLab repos. There's something rewarding about self-hosting and not being beholden to the whims of third parties.
Re: Days without GitHub incidents
#94Earlier quoted context omitted.
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
#95Earlier 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.
"AI coders submitting 25 PRs within an hour of an issue being filed, GitHub bears the brunt of that....". What "brunt"? These are not large numbers.
AI coding has made this orders of magnitude bigger.
The individual numbers are small, but they add up quickly.
Re: Days without GitHub incidents
#96Earlier 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?
The "model" - GH effectively allowing an overload of their infra - is already broken
> How would a random kid in a 3rd world country ever get noticed enough to enter a trust circle
By submitting a quality change with a clear description, preferably with unit tests? Is that no longer considered an acceptable hurdle?
Re: Days without GitHub incidents
#97Earlier quoted context omitted.
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
#98Earlier quoted context omitted.
You don’t know that it was “their mistake.” Unless you’ve personally successfully scaled a suite of nontrivial services equivalent to GitHub’s to accommodate an unexpected 14x increase in traffic, you respectfully have no basis for such an assertion.
I have. You could argue the scales are different, but computers are also faster now. So, argument to credentialism out of the way... What should we do as consumers if a provider that is a defacto monopoly due to network effects stops functioning? https://news.ycombinator.com/item?id=47947719 https://www.linkedin.com/in/jharasym/
Scale is everything and a faster computer doesn’t always help. Vertical scaling has limits, and complex distributed systems are complex.
Since you seem to possess a diagnosis and remedy with a reasonable amount of certainty, I’m sure they’d love to hear from you and have you fix all their problems for them. Especially if you can do it while not making the problem worse in any dimension.
Re: Days without GitHub incidents
#99Earlier quoted context omitted.
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?
> would break the entire model The "model" - GH effectively allowing an overload of their infra - is already broken > How would a random kid in a 3rd world country ever get noticed enough to enter a trust circle By submitting a quality change with a clear description, preferably with unit tests? Is that no longer considered an acceptable hurdle?
But the proposal is to specifically disallow that unless the person is already known.
That is the model today, the one that people want to get rid of.