• @Geek_King@lemmy.world
    link
    fedilink
    4010 months ago

    I used to use nothing but Intel every time I built a new gaming PC. My last build in early 2021, I went with AMD 6900, and I’ve been real happy with it. I had been planning on going back to Intel for my next build, but this has spooked the shit out of me.

    • BombOmOm
      link
      fedilink
      50
      edit-2
      10 months ago

      The worst part is Intel has known about this issue since at least 2023 and did not take ownership of the issue. They did not proactively recall defective chips, they just sold them and hoped people would not return the defective product.

      It took teams of individuals cataloguing error rates to confirm this issue exists and for media like Level 1 Techs and Gamer’s Nexus to confirm and get the word out.

      It is a complete damnation of Intel that the ‘solution’ was to brush this massive issue under the rug and fuck over customers.

      • @ChicoSuave@lemmy.world
        link
        fedilink
        2710 months ago

        Graybeards know Intel has always been this shitty. There was a time when Intel and AMD used the same socket type, the legendary 386 and 486 generations were amazing. Intel needed a way to stand out from AMD and Cyrex, a long forgotten big chip maker that died when Intel walked away from the x86 naming convention and used their own socket type to make the Pentium. But that’s a story for someone else to tell at another time.

        Intel started from betrayal and grew out of spite. When it flourished it would use its influence on governments to avoid including bids on non-Intel computers. The Wiki article for Intel has a section for legal issues AND a separate section for product issues, a distinction needed for very few other companies. Intel has always been underhanded and evil - they just also happened to design fantastic CPU architecture for a while.

        • @ramble81@lemm.ee
          link
          fedilink
          710 months ago

          True, but don’t forget the K6-2 and how they screwed up the paths so when it heated up it’d short itself out. Coupled with the lack of a thermal regulator and you could turn an AMD into a pile of silicon.

      • @Blue_Morpho@lemmy.world
        link
        fedilink
        710 months ago

        I find it intriguing that despite Intel hitting its numbers and getting great press for the past few months, the stock has been on a sharp decline. It’s as if some knew the bad news was about to hit soon.

      • Phoenixz
        link
        fedilink
        710 months ago

        As large companies yend to do, always thinking, hoping, that people won’t find out. But people in the end always do. There are always these nerds (compliment) who won’t give up, go to the last bit to find out what’s happening and they’ll always find it. Why be so stupid?

        I present to you: Middle Management!

    • @Beryl@lemmy.world
      link
      fedilink
      2810 months ago

      I honestly don’t understand why you’d go back to Intel these days. Performance is only comparable if Intel chips guzzle like twice the wattage, and they’ll make sure you have to also change your mobo by conveniently switching sockets every two years. What’s the upside of going Intel?

  • BrightCandle
    link
    fedilink
    3110 months ago

    I suspect there are going to be many lawsuits all over the globe about this. The situation is so bad and so expensive Intel has decided to weather all those lawsuits and class actions instead of doing a recall. That suggests to me odds are everything they have made since the 13th Gen is soon for an early tech graveyard.

  • @InFerNo@lemmy.ml
    link
    fedilink
    010 months ago

    Thank you Microsoft, forcing everyone to buy new CPUs just to be able to run their latest iteration of Windows.

      • qaz
        link
        fedilink
        12
        edit-2
        10 months ago

        Windows required CPU’s to have certain extensions/instructions to use the newest version, which might have required buying a new CPU and thus getting one of the affected ones. However, I don’t think it’s reasonable to blame Microsoft for this.