Live data from Hacker News

Red Squares – GitHub outages as contributions

red-squares.cian.lol

171–175 of 175 posts

Re: Red Squares – GitHub outages as contributions

#171
post #123

Earlier quoted context omitted.

The avalanche of same comments to every meme tier post about this is the opposite of curious. Very little discussion of any merit happens on these posts. It’s mostly bandwagoning and repeating the same comments they read on the last iteration.

I agree... https://news.ycombinator.com/item?id=48026924 Yet here we are. I just don't feel comfortable with you defending the trillion dollar company as if we owe them something, or as if they're somehow the victim in all of this. I can buy that there's more demand for service, but; A) They are the ones pushing the AI hype (microsoft especially but github too) B) These issues existed before the AI hype anyway and, o…

Assuming scaling is the issue (and I have no reason to believe they're lying about that), the obvious solution is to rate limit to below what the system can handle. Start saying you can't make a new account, you can't make new repos, you can't push. That's not something ICs are empowered to do (apparently) so it falls on management to empower them to be able to say that to customers.

Or so I imagine office politics to be there. I've never worked ah Microsoft specifically though I have worked in corporate America at other large companies.

Re: Red Squares – GitHub outages as contributions

#173
post #114
post #76

Earlier quoted context omitted.

> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…

> It's a waste of time to rewrite the UI and push AI tools when you can't even keep the site lit. This is a flawed argument. There are many designers and frontend engineers there who have zero role in improving site reliability. They might as well keep doing their jobs, instead of having the CSS wizards and art school grads team up and try to crack Azure.

Well, it depends.

Managing and coordinating a bloated organization always has a cost and an overhead, from communication issues to technical inefficiencies.

And I also doubt the frontend/backend divide is so clear. I would bet quite a few developers are working on both.

Re: Red Squares – GitHub outages as contributions

#174
post #4

The memes are really painful now. I feel for the team that's is trying to survive underwater.

$250k can do a good job of easing meme-induced pain. "survive underwater" what a joke. Yes, there will be good engineers there who will be sad to see it go this way, but they choose to be there, get paid better than 99% of humanity for that.

You are removing the humanity from these people. Yes some don't care and just take their salaries. But I'm sure some people if not majority is stressed due to the situation.

Re: Red Squares – GitHub outages as contributions

#175
post #29

Another reminder that a self hosted git repository would have more uptime than GitHub and centralizing everything to GitHub was a very bad idea. [0] [0] https://news.ycombinator.com/item?id=22867803

That depends entirely on where you host it. My PC has more downtime than GitHub does. It's only up enough to push to it ~75% of the time (I do use it as a ssh remote fwiw, but most projects get pushed to a VM that only starts on login, and my PC itself isn't always running).

If you're working on an oss project (ie distributing source anyways), probably better a good idea to mirror to GitHub as a backup anyways, let Microsoft pay for backup+bandwidth for you.

Post reply on HN