• Rob Bos@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    7 hours ago

    I supported windows for a while… I’m not sure I went more than an hour or two without going to command line to fix something or another.

    • Mic_Check_One_Two@reddthat.com
      link
      fedilink
      arrow-up
      4
      ·
      3 hours ago

      Let’s at least not exaggerate, because it’s not particularly useful if you’re trying to get someone to switch. If someone is on the fence about it and sees comments like yours, they’ll be more likely to go “oh well I don’t have those kinds of issues with Windows, so it must just be them.” The vast majority of Windows users (office workers, people using it to check emails and browse Facebook, people just using it for Steam, etc) will literally never need to use CLI.

      If you’re needing to use CLI every hour or two on Windows, that sounds more like you’re using the wrong tool for the job. Essentially, you’re trying to use a drill when you need a hammer. A drill may function as a hammer… But it’ll probably take a lot of extra effort. And it’ll likely end up damaging the tool, because you’re using it for something it wasn’t designed to do.

      • Rob Bos@lemmy.ca
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        3 hours ago

        I was a windows sysadmin doing mostly software deployment and automation. I was definitely an edge case. Point is, windows has a command line and requires it for a lot of tasks.

    • Flax@feddit.uk
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      If something is broken in windows, tough luck. I always find if something is broken in Linux, someone has a fix