this post was submitted on 19 Mar 2025
1711 points (100.0% liked)

linuxmemes

23841 readers
474 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Nugscree@lemmy.world 19 points 3 days ago (6 children)

    The main problem still is that for some configuration you still need to use the CLI, the average user does not want to touch that no matter how powerful it is, they want a fully functional GUI that lets you so exactly the same thing but by clicking on buttons. Pair that with drivers that either do not exist or will not work for (some) of your hardware, odd crashed like the Bluetooth stack crapping out and not working anymore until you restart the system, or the system that hangs from hibernation with a black screen. So unless those hurdles are tackled the Linux adoption rate will stay low because the average user wants a system that works, and not one they have to debug.

    I've been on and off different distros of Linux since Ubuntu 6 using Pop_OS! as my daily driver for work a few years now, and the same problems I had then are still here today which is a shame honestly.

    [–] Nalivai@lemmy.world 11 points 3 days ago (29 children)

    the average user does not want

    The average user wants their problem gone. And will use whatever helps. Windows users were editing register and editing ini files since Windows was an addon to DOS, and continue doing it. For a literate person there is absolutely nothing more inheritly more intuitive or easy in clicking a checkbox in a fifth submenu than entering a command in a console. Stop perpetuating this weird myth.

    [–] MystikIncarnate@lemmy.ca 16 points 3 days ago (1 children)

    This is correct. I work with the "average user" of technology daily as IT support, and honestly, they don't give any shits at all about why it's messed up, or what needs to be done to correct the problem. Box broken, make fix.

    The argument that I think the poster is trying to make is that, if a user needs to do any self troubleshooting, which is basically inevitable with technology at the moment, having to use a CLI to get things done is undesirable for the average person. They barely want to bother opening control panel in Windows (or the new "settings" app.... Ugh.) nevermind understand any of it.

    Box broken. Make fix.

    [–] Nugscree@lemmy.world 8 points 3 days ago (1 children)

    It's not a weird myth, have you ever worked with average users? Some of them have trouble opening a PDF or don't know how to import a CVS file in Excel. Power users have always been tinkering in their OS that's nothing new, but I'm talking about the average Joe.

    [–] Nalivai@lemmy.world 1 points 2 days ago

    People you described don't have better or worse time with different types of user interfaces, it's all incomprehensible to them. Average Joe with zero skills can't check boxes in some weird menus, just as they can't write text in a weird black box. We're talking about people who are at least a little curious about their OS.

    load more comments (27 replies)
    [–] Jhex@lemmy.world 8 points 3 days ago

    The main problem still is that for some configuration you still need to use the CLI, the average user does not want to touch that no matter how powerful it is,

    At this point this is just misinformation... you can easily live and configure everything an "average user" would via GUI in Ubuntu (and most of it's derivatives) or anything running KDE Plasma as a desktop

    The reason must of us still CHOOSE to use CLI is because it's powerful but unless you are crazy as I am and running Hyprland as a daily driver, you really do not need CLI...

    PS: I fucking love Hyprland! hehehehe

    [–] _carmin@lemm.ee 6 points 3 days ago (2 children)

    I dont know wtf you are using, KDE and Gnome dont use the terminal and Bluetooth has never crashed for me. Your shit is all fucked up

    [–] MystikIncarnate@lemmy.ca 11 points 3 days ago (1 children)

    IMO, this is a demonstration of the problem. You're blaming the poster/their equipment. Rather than any real solution to the problem the defacto answer is "well, it works for me so what's wrong with you?"

    I've never heard this kind of toxicity from other communities (like the apple/Windows crowds). Often you'll get useful answers indicating what to check or pointing to another resource. There's always the chance that the hardware is busted, but let's face it, in the modern era, that's far less likely to happen now than it was even 10 years ago.

    Immediately blaming the user for their issue isn't going to solve the problem, nor does it endear any average user to the Linux community or the Linux OS. This attitude is not going to help adoption even if the posters concerns are invalidated by newer/better drivers/software, and all they need to do is update, and/or try again.

    This kind of statement actively harms Linux adoption.

    [–] _carmin@lemm.ee 3 points 3 days ago (2 children)

    Sorry I meant to say I dont even remember how many years ago I saw anyone with Bluetooth problems. Look how you conveniently ignore the fact Kde and Gome dont use the terminal contrary to what you had stated. Your shit is all fucked up.

    [–] MystikIncarnate@lemmy.ca 1 points 2 days ago

    Bitch please.

    Just try to install a program that isn't in the repo without dropping to the CLI.

    I dare you, I double dare you.

    [–] Nugscree@lemmy.world 3 points 3 days ago (1 children)

    https://www.omgubuntu.co.uk/2025/03/ubuntu-2404-bluetooth-connect-fix Bluetooth issues are still a present problem in Ubuntu 24.04LTS, which appear to be fixed in 24.10. If I want to restart the Bluetooth stack I have to do that in the terminal, on Windows, you go to the services window and restart it from there (not that I've ever had a Bluetooth issue on Windows). Just because you don't experience it does not mean it does not exist, you appear to be one of those toxic it works on my machine people.

    load more comments (1 replies)
    [–] Nugscree@lemmy.world 3 points 3 days ago* (last edited 3 days ago)

    It's a brand new (one year old now) Thinkpad X1 Carbon, with a clean installed Pop_OS! system, so I don't know why it does that, but it has done it at least ten times since I got it. Also after installing VirtualBox I've been have kernel panics occasionally when shutting down the system Β―\(ツ)/Β―

    Yeah, that sums up my experience quite well.

    [–] Kichae@lemmy.ca 3 points 3 days ago (2 children)

    There are also just a lot of personalization options that just aren't there, particularly for power-lite users, because Linix power users use the terminal for everything.

    Like, heaven forbid you want a full featured, advanced file manager or something, but aren't interested in learning bash scripting...

    [–] _carmin@lemm.ee 5 points 3 days ago (1 children)

    Are you truly saying personalization is not there on linux but Windows has it? LoL

    [–] MystikIncarnate@lemmy.ca 3 points 3 days ago (3 children)

    I'm pretty sure they're saying that customization, while present in Linux, is not accessible to most because of a lack of GUI options to configure a nontrivial number of the customization settings.

    [–] _carmin@lemm.ee 2 points 3 days ago

    KDE can configure more things than there are atoms in this world. And All other DE are way more advanced than windows all through the GUI. So their point remains garbage

    load more comments (2 replies)
    [–] AugustWest@lemm.ee 3 points 3 days ago (10 children)

    you want a full featured, advanced file manager or something

    Which means you are shit out of luck in windows, but comes by default in Plasma. Go figure.

    load more comments (10 replies)

    I'd argue that as Windows continues to abandon its (relatively) sane configuration UI for the newer useless Settings screens, it has reached the point where it really is sometimes easier to just look up what you need to do in Powershell.

    This problem is only getting worse over time, so I don't think it's fair to hand the win to Windows.