• blind3rdeye@lemm.ee
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 year ago

    Those are (made up) problems that might arise after you’ve already installed it; and I doubt Microsoft’s guide says much about them.

      • blind3rdeye@lemm.ee
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        Umm… I really don’t know why you’re coming at me with some sarcastic anti-linux shit right now. All I said was that it was pretty easy to install. I didn’t say or imply that it was problem free. As for the problems being ‘made up’, I made a reasonable assumption that GRUB doesn’t care what day of the week it is - and so what you described was hypothetical only.

    • Phen@lemmy.eco.br
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      While I agree with you, the issues described are definitely not made up. Linux tends to remove proprietary drivers on every update and the open source drivers for Nvidia still fail with a lot of hardware.

      • EddyBot@feddit.de
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        this only happens if you install proprietary drivers manually and not through the software center (or package manager for the cli folks) on almost every given linux distro
        this is why no sane linux user recommends installing download scripts from websites, you rely instead on your package manager to handle everything

        • Phen@lemmy.eco.br
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          1 year ago

          I never installed any driver in any way other than the software center and it happened to me in every single update for several years until I finally bothered to search how to configure the update process to stop doing it (last month).

          Multiple machines, distros, DEs, you name it. None of them ever not had this problem.