3 ms·
Honestly? If the problem is scalability, just rate limit git commands on free accounts already. Nobody realistically need to push multiple times per minute, an
by guhcampos 1mo ago
Honestly?
If the problem is scalability, just rate limit git commands on free accounts already. Nobody realistically need to push multiple times per minute, and that alone is bound to trickle down to anything that triggers on commits and pushes.
- brazukadev 1mo agoSure. The problem is just an easy fix that nobody there thought about yet.
- guhcampos 1mo agoMy point is: they blame it on scale. If that's the story they want us to believe, then they have to explain WHY such a simple fix isn't possible. There may be non technical reasons for it, even: legal, or PR, but if they want me to believe the "scalability excuse" they need to convince me they're trying.
- materielle 1mo agoI don’t know, but typically when orgs don’t make logical decisions, it’s because internal politics are incentivizing something else. I suspect that rate-limits would fly in the face of a lot of narratives like “Azure is ready for hyperscale”. And getting eyes on Github is probably a part of their Copilot product strategy.
- pydry 1mo agorealistically the problem is vibe coding.
- roncesvalles 1mo agoThe problem is when you stuff your codebase with so much unreviewed vibecoded slop that engineers lose their grasp on how it all works.
- NewJazz 1mo agoKeep pulling the lever, uptime has to improve eventually!
- cluckindan 1mo agoJust create an MCP server for the uptime history and tell Claude to optimize the business.