Why are distro communities turning linux more and more into Windows and Mac OS clones?

This is why I use Arch.

  • GreyEyedGhost@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    28 days ago

    As someone who read at least 2/3 of the DOS 6 manual when it came out, and have used a variety of Linux flavors as well, a command prompt is the least helpful interface devised. What do you type there? How do you let the computer know when you’re done typing? If the answers seem obvious to you, think about why, and what on the screen would point you that way if you hadn’t had training. People are very visual, in general, and a simple interface such as a mouse that directs focus and has a minimal amount of interaction options is far easier to get started with, especially if the GUI has culturally intuitive icons (save needs updating).

    I don’t think the power of the command line, or text interfaces in general, can be overstated, but even the most helpful text interfaces, such as those found in some IDEs, require prior knowledge to be useful. This isn’t going to work for the majority of people.

    • taladar@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      6
      ·
      28 days ago

      If you think GUI is intuitive you have never worked in support and despaired at people trying their best to get “simple” concepts like “left-click” vs. “right-click” wrong.

        • barsoap@lemm.ee
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          2
          ·
          28 days ago

          At least there’s only a single way to tell the computer “ok, execute this command”. And you see the command written in plain text before you.

          And, no, no useful interface is intuitive because computers just have too many functions. There’s no intuitive appliance in the world with more than a temperature knob and a timer knob. Knowledge is always required, be that cultural or by RTFM.

          • GreyEyedGhost@lemmy.ca
            link
            fedilink
            English
            arrow-up
            4
            ·
            28 days ago

            Unfortunately, for the scenario I was replying to, a lot of the times when you’re doing support, you can’t see the user’s screen and are limited to verbal communication, so verifying what they typed or the output can lead to just as many problems. Any support scenario where you’re talking the other person through a series of tasks will be very dependent on how familiar each person is with the task you’re supporting. And no one Rs TFM these days, if you even get one.

        • taladar@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          28 days ago

          It is literally easier to explain to them how to do something on the command line than in a GUI, both in documentation and over the phone. That doesn’t mean they will ever discover how to do something in either interface on their own but I don’t really expect that from the people who make paper notes of the step-by-step process in GUI workflows anyway.

          • GreyEyedGhost@lemmy.ca
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            28 days ago

            Just try to verbally describe the difference between a bracket, brace, or parenthesis, or forward slash vs backslash. I’m sure it will be fine. But absolutely, a text-based interface is easier to describe in text.