• baines@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    3
    ·
    6 days ago

    ms literally pushed a vibe coded update that boot lopped multiple dev machines for a week before we resolved it

    technically it was fixed same day but only because we have regular nightly images and other machines

    that alone should be enough of a reason, this is just more shit on the camel’s back

    but so you know I’m not downvoting you, nothing you’ve said is unreasonable, I just really have no patience with current tech companies and clearly lemmy is sick of ms’ shit

    • Fizz@lemmy.nz
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Microsoft pushing a bad update and breaking dev machines is an issue with your it department. Every single OS pushes bad updates thats why you stagger your releases through rings so you can catch the issues early and minimise downtime.

      Imagine if we stopped using linux because of a bad update.

      • baines@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 days ago

        don’t act like this is normal

        i can’t think of a linux release in the 22+ years that’s had a non recoverable boot loop

        and who says it wasn’t staggered? doesn’t do a damn thing for those in the release group

        • Fizz@lemmy.nz
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          3 days ago

          You just said you recovered the windows boot loop.

          Linux breaks booting all the time. Its so common its every linux user knows how to fix it. Pick the distro and you’ll find tons of boot issues after major updates.

          • baines@lemmy.cafe
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 days ago

            yea recovered by reinstalling an image from before the update, the system was a complete brick otherwise

            it took microslop 3 weeks to fix their shit, google it if you are confused, it wasn’t a limited hardware exposure issue, it was bad code

            we’ve been running rhel stable for decades with never a single example like this, i’m not talking about one off hiccups, i’m talking about the entire main line being busted

            pulling an example of loops from some random linux unstable distro or beta is meaningless

            to claim otherwise is bullshit, again this is not normal, even ms hasn’t been this bad since early vista