• BrightCandle@lemmy.world
    link
    fedilink
    arrow-up
    51
    ·
    4 months ago

    Either Intel is extremely incompetent and genuinely has no idea what is causing this problem or it knows full well is doing all it can to drag this out and avoid recalls. This saga has been going on all year now this is getting ridiculous.

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      19
      ·
      edit-2
      4 months ago

      All I can say is I would absolutely not buy an Intel processor right now and maybe not for the next few years.

      It’s just not worth the hassle finding out in six months that your system is unstable and you need to change the processor to fix it, and not knowing if that new chip is any better than the one you just removed.

    • BeardedGingerWonder
      link
      fedilink
      English
      arrow-up
      8
      ·
      4 months ago

      I’d imagine chip design is sufficiently complex that you could both be competent and not have a fucking clue what’s causing this. A recall is bound to be cheaper than the impact this is going to have on customer trust. Not only are they the lower performance chips, they’re buggy lower performance chips.

      • Entropywins@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        4 months ago

        They have a clue…probably had a clue before they shipped. I chat up the engineers where I work and they always figure out the what, how and why somethings fucked when more than expected failures pop up on a wafer or God forbid in the customer’s production units like a car or radar or medical equipment.

        • trolololol@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          Ask the c suite, they’ll say no clue. Ask the engineers, they’ll say give me x time and I’ll tell you why.