• Nah, but there were some Linux evangelists claiming this couldn’t possibly happen to Linux and it only happened to Windows because Windows is bad. And it was your own fault for getting this BSOD if you’re still running Windows.

    And sure, Windows bad and all, but this one wasn’t really Microsofts fault.

    • rottingleaf@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      4 months ago

      The sane ones of us know well that a faulty driver is a faulty driver, but! Linux culture is different. Which is why this happened so spectacularly with Windows. EDIT: and not with Linux

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        I’ve had the proprietary Nvidia driver crash my whole system a few times. Hoping their new open-source driver (not nouveau, I mean the new out-of-tree open-source one) is better.

    • Ferris@infosec.pub
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      if they dont know the boot sequence is a thing maybe their opinion on this doesnt really matter 🤷🏼

      • vext01@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Yeah, it supports kernel modules, so is also vulnerable to bad third party kernel code.

        • Petter1@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          🤔if nobody makes a third party kernel module, then there is still no risk

          • vext01@lemmy.sdf.org
            link
            fedilink
            English
            arrow-up
            0
            ·
            4 months ago

            Also, even if they do, you can choose to not load it.

            It amused me that so many people had this installed, but had no idea what it was for.