all those layoffs really paying for themselves

https://akko.wtf/objects/fd38c467-a729-40b4-be5c-367c64d879e5

you are viewing a single comment's thread
view the rest of the comments
[+] 39 points 6 months ago (5 children)
  • [–] 51 points 6 months ago (1 child)

    Look, GitHub is an entry-level offering for the general public. If you want true worst-in-class performance you have to go with Azure DevOps.

    GitHub simply doesn't have features like build steps that randomly take ten times as long as usual to complete for no reason, an inability to refer to a PR just by its ID even though it's unique, or a navigation that makes no sense at all. Sure, you get that four-eights availability but do you get pipelines that reliably fail even though they worked just fine yesterday and nobody changed anything? Those are enterprise features for companies that pay big money to get the worst damn Gitlab clone money can buy.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 17 points 6 months ago (2 children)

    If Azure had an 11% downtime, then I'd consider it a blessing. 19 hours a week when you'd be free of using the damned thing. But no, it just stays up and taunts you.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 6 months ago* (1 child)

    But does it really stay up, or does it just suffer random undocumented service degredation near constantly? ;)

    Can't tell you how many times I've built some basic automation off the fact that certain operations through Graph are effective basically instantly, only to have to add increasingly long timers between steps like a week later when Azure suddenly decides that it's done being "nice".

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 6 months ago

    I have tested stuff in Azure for like a week, and that was enough to understand it is completely unreliable. Bring up some test VMs with terraform, an hour later one of the nics are gone. Like, thanks, but I needed that.

  • source
  • parent