• Ooops@kbin.social
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    edit-2
    9 months ago

    Ok, something didn’t work, I now have to figure out what driver wasn’t supported and what I need to download.

    Unlike in Windows where you never need to download drivers. As executable binaries you have no chance of checking. Sometimes from very questionable sources. And actually you can be happy if it’s only a driver. Installing random 3rd party tools just to get basic functionality is a thing.

    people on forums are helpful

    Which also happens for Windows. But rarely. And if they really try… then there are still 10 different answers to a single problem and you have to test which one works for your specific version (no, chosing the most recent one sounds logical but is rarely the answer).

    Now I gotta figure out this command line thing. Oh cool some people built GUIs for certain stuff so i don’t need to play with the command line

    Which in what way is worse then editing random obscure values in the registry? Because it’s a window you type in. And in the worst case even the Windows help starts with poweshell nowadays, which is exactly the same.

    And then at some point I got stuck because of file permissions.

    That’s a solveable problem. Unlike in Windows where they put file permissions on top a file system not having them in a weird unintutive way. And don’t ever try to change the wrong permission as an administrator as that’s simply not allowed. After all you don’t own your Windows PC, MS just gratiously allows you to use it.

    So, you see… it’s all a matter of perspective.

    • Hawke@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      9 months ago

      10 different answers

      No there’s only ever one answer and it’s “have you tried ‘sfc /scannow’?” But it never works, even if it finds an alleged problem.