cross-posted from: https://lemmy.blahaj.zone/post/41604641

all those layoffs really paying for themselves

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

all 4 comments

sorted by: hot top controversial new old
[–] 30 points 6 months ago (3 children)

It seems like a bunch of the big tech companies are shuffling compute around rather than getting more. Are we hitting the limit of the currently available compute, or is this just MS being bad at things?

  • source
  • hideshow 3 child comments
  • [–] [S] 19 points 6 months ago (1 child)

    Yea, that shoe company (all birds?) doing a pump and dump by saying they're going to turn into a compute company really shows a big issue with the market, but also with available resources. I'm sure MS is just managing a lot poorly, but the rate at which they are desperately building data centers regardless of where leads me to believe they need a lot and fast, though I think once they start pricing appropriately they'll see demand plummet.

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

    “Pricing appropriately” right. This really reminds me of the Web 1.0 bubble. So many startups with so many ideas and all this venture capital being pumped into them. And once people realized none of these businesses could ever be profitable, the bubble burst, leaving many people unemployed. Mainly tech workers. This time I fear it will be more than just tech workers.

  • source
  • parent
  • 8 comments in c/microblogmemes@lemmy.world view that post
    [+] 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
  • [–] 12 points 6 months ago

    Ah, I see where the misunderstanding lies

    It's actually "five neins"

  • source
  • [–] 6 points 6 months ago

    Nine fives, better than a coin flip.

  • source