• 1 Post
  • 254 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle







  • There was a two-generation long lithography issue that they had not been able to solve. You are grossly understating the technical scope of the problem, as well as the trust issues Intel themselves created with the way they handled the whole debacle.

    I’m not ever going to buy a 13/14 gen Intel core unless it’s at absolute bargain basement prices. In a professional IT context, nobody in purchasing departments should be buying the impacted SKUs in the affected date range (and practically, that means “they won’t buy those SKUs, full stop”).












  • gravitas_deficiency@sh.itjust.workstoGaming@lemmy.mlIntel Crashes
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    2 months ago

    …after knowing for damn sure it was a serious issue in two successive process generations.

    There is no way this happened without a LOT of people knowing EXACTLY what was happening, and covering it up. The DoJ should really kick off an investigation into the situation, because it’s pretty obvious there was malfeasance at multiple levels. That, or their leadership and QC processes are both so categorically inept that one could argue the company should be straight up nationalized as a critical strategic asset.