this post was submitted on 10 Dec 2023
1334 points (98.3% liked)

linuxmemes

21172 readers
902 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Dmian@lemmy.world -2 points 11 months ago

    Oh! I’m in no way discussing the viability or economy of it. Of course in a lot of cases, creating a batch process, for example, may be the better choice. And I would also say that in some cases, using a CLI may be way more efficient that creating a GUI for something.

    My statement is just that it can be done. Nothing more.

    And in some cases, it’s not even that hard, it’s just that maybe people are used to do things using terminal. Or there may be other reasons. Who knows? But I would like for programmers to, at least, consider the option in some cases. You may be surprised at the things that can be achieved with a good GUI, and how it helps less tech-savvy users.