Let the apologists have a field day in the comments.

  • RejZoR
    link
    fedilink
    English
    295 months ago

    It’s why I’m so furious about Linux in general and how every god damn intent to change almost any setting begins with “open Terminal…”. I don’t want to use the damn Terminal. It’s 2025 now, put the god damn basic ass settings into control panel so I can click it without first spending half an hour to find a long noodle of commands for Terminal that I don’t even understand, paste it in and hope for the best.

    Like, I had issues with Bluetooth module in my laptop and I wanted it disabled so my BT USB dongle is main. In Windows I’d just go to Device manager and disable that device. Done. On Linux I spent hours diging on how to disable BT module and weed out all the bullshit on how to disable the function itself because I need it, just not from the fauly module. Then I spent asking on Reddit where someone finally posted a working Terminal command that I had to save into config file using Terminal because file manager is to stupid to save it into system area by just asking me if I want it there or not. I now have a folder with config file and instructions on what stupid ass copy command for Terminal I need to use to copy the config file where it needs to be.

    Just so much unnecessary bullshit for something that could be done in literal 5 clicks at worst if the damn option was in GUI to disable single device on the system. Also fun fact, Linux has a “wireless devices” tool, command line one and it uses device ID to apply it and the fucking ID changes every time for the device so you can’t make a permanent setting. I kid you not. I’ve never seen anything more idiotic.

    • @conartistpanda@lemmy.world
      link
      fedilink
      95 months ago

      How ungrateful! Do it yourself? It only takes learning how to program. Thats like… a 45 minutes search. 80 if you want to learn how to program an OS from scratch.

      • 𝕾𝖕𝖎𝖈𝖞 𝕿𝖚𝖓𝖆
        link
        fedilink
        English
        6
        edit-2
        5 months ago

        Everything I know about bash I learned by spending a decade copy-pasting random commands I found online into my terminal.

        It’s really that easy. You’ll be sudo apt update-ing with the best of them in no time when you spend a decade copy pasting commands you found on the web to your terminal.

          • 𝕾𝖕𝖎𝖈𝖞 𝕿𝖚𝖓𝖆
            link
            fedilink
            English
            2
            edit-2
            5 months ago

            True story - I keep blank audio CDs around because my cars have CD players. The fact that I still burn CDs is another story, but Debian is still small enough to fit on a CD-ROM. So I keep a backup of Debian 12 on a CD-ROM so I don’t have to lose a flash drive to that task. Very convenient. And I’ve broken my system a few times tinkering. I’m not even sure how. But hey, I love to go fast and break things. I probably made an edit to a file long ago and forgot about it and now it borked stuff. It happens.

            At this stage, I’ve got it down pretty good. If I break my OS, I can plop in my boot CD, use rescue mode to back my home folder up to a flash drive and wipe the system. I keep lots of other things on extra HDDs so all I ever wipe is my boot SSD. I have an Nvidia GPU so before I log in for the first time, I just get back into rescue mode and set up my root password, user account and password, reclaim my home folder, change ownership to the new account, set up fstab, and install drivers and programs before ever logging in as my user for the first time - all from the console.

            As for data loss, I haven’t lost any. I have never needed to wipe my hard drives so as long as my home folder is intact, retrieving that is easy enough. I don’t keep just one copy of irreplaceable files, either. While my phone does back up my stuff to Google Drive, I keep additional copies of my favorite pictures and videos on DVDs. Three copies, on at least two different media, one of them off-site.

            Breaking your OS is really not that big of a deal once you know how to retrieve stuff without it. You don’t even need CDs lol The boot CD is just for convenience. You can bork the system on a computer with just one storage device and as long as you have two flash drives, you can get it all back pretty easy.

            But I’m only here after years of experience in bash. If I went back ten years with a busted laptop and told my 22 year old self to use lsblk, mount, and cp to copy the home directory to a removable device all in command line, younger me would probably cry lol

      • @Nalivai@lemmy.world
        link
        fedilink
        35 months ago

        You don’t need to “learn how to program”, whatever the fuck you mean by that, to interface with texting terminal. We’re interfacing via text right now and you seem to do it just fine, you don’t seem to need a selection of colourful boxes to understand what I am saying

        • @conartistpanda@lemmy.world
          link
          fedilink
          25 months ago

          You’re asking average people to learn a new language so they can install software (thats not on the stores) or to do some beyond basic configs. Why should they bother learning bash when they could just use windows and learn somethint else with that time?

          How many times did i find a post telling me to create a weirdly named txt just to change my touchpad settings? Its not trustworthy for noobs. How is a noob suposed to know if a command on a tutorial is safe or not if many linux distros let you destroy them via rm -fr? Are they supposed to search each and every command before they use them? Im sure lots of people rightfully reject using the terminal (and therefore linux) for this reason.

    • @kreskin@lemmy.world
      link
      fedilink
      45 months ago

      I don’t want to use the damn Terminal.

      Unfortunately the people who code prefer not to use guis if they can help it.

      • @Shapillon@lemmy.world
        link
        fedilink
        24 months ago

        This, so much.

        I genuinely could have said something very similar but in reverse.

        I don’t want to use a GUI that does stuff that I don’t understand behind my back. Terminal is simple. You read the man, the output, the return value, etc and you just know what happened.

        imhi GUIs are a pita proportionally to how complex what you’re trying to do is.

    • Darren
      link
      fedilink
      English
      15 months ago

      I have a similar rant with Docker.

      On macOS there’s a Docker app. You can use it to install stuff, see what it’s up to, restart it and whatnot. On Linux you have to remember what commands you have to use in Terminal.

      Why?!

      There are loads of us out here who would appreciate a more user friendly way to use FOSS, but we’re made to feel like fuckin noobs because we don’t want to spend ages typing in commands when we could just press a couple of fucking buttons.

      Anyway, apart from that I’ve been enjoying my adventures in Linux.

      • JackbyDev
        link
        fedilink
        English
        5
        edit-2
        5 months ago

        You’re probably talking about Docker Desktop. It may not be on Linux (or at least your distro or whatever) because it’s not actually FLOSS. If you want to use Docker with a GUI I’ve had success with Rancher Desktop which is made by SUSE and is FLOSS. It’s still Docker (unlike podman which is not technically Docker), but it has a GUI for some stuff too.

        I tried installing Docker Desktop at work and realized the license doesn’t actually allow that without paying. It was weirdly difficult to install Docker by itself on Mac so that led me to finding Rancher Desktop.

    • RedSnt 👓♂️🖥️
      link
      fedilink
      3
      edit-2
      5 months ago

      I don’t mind using the terminal, but how the fuck am I going to remember something like kwriteconfig6 --file startkderc --group General --key systemdBoot false? (In fact, there aren’t even man pages for that command). Like the scribbles of a mad man I’ve had to put down commands like that in a sort of personal instructions manual, because ain’t no way I’ll remember these commands by heart.
      And you often end up just saving the most used commands as aliases or functions in the .bashrc meaning you don’t retain the syntax for the commands you use. Well, maybe I’m a unique case of fish memory… The thing about humans is that we greatly rely on our vision, and having GUI’s to show what’s possible greatly improve ones understanding of how to manage it going forward.

      • @Oinks@lemmy.blahaj.zone
        link
        fedilink
        24 months ago

        kwriteconfig6 is barely documented because you’re not really supposed to use it. All of the settings that users are expected to change are in the nice settings app that Plasma ships with. Using kwriteconfig (or equivalently a dconf editor on GNOME) is like editing the registry on Windows; you are implicitly opting into more power, out of most guardrails and into potential breakage. The UX being a bit questionable (though honestly it’s really not as bad as you’re saying, it does exactly what it sounds like it will do?) is to a degree intentional, because you’re not supposed to be using this unless you know what you are doing.

        • RedSnt 👓♂️🖥️
          link
          fedilink
          14 months ago

          Tbf, disabling systemD autorun is the only thing I’ve ever user kwriteconfig6 for, because with it enabled bash scripts don’t run correctly.

      • RejZoR
        link
        fedilink
        English
        25 months ago

        This is why GUI exists. So you don’t need to memorize idiotic and long commands.

      • NSRXN
        link
        fedilink
        3
        edit-2
        4 months ago

        I keep all the little snippets like that in an org-mode file, and write notes about what I was doing and why, and org-babel can even execute the code right there in the document.

        and it’s not even running a terminal!!

    • Phoenixz
      link
      fedilink
      65 months ago

      KDE has an enormous system settings GUI.

      Having said that, I use the console for like 90% of tasks. Basically I use either the GUI browser, an editor (I’m a dev) and the console through yakuake.

      I use the console because it’s way WAY more efficient to get shit done. What teo windows admin do in 30 minutes I do in 30 seconds, and that was an actual event where we had to change DNS configurations inna large amount of customer servers.

      Command console is not old tech, it’s efficient tech.

      Having said that, most normal users shouldn’t have or need to access the console either and for most of the time, this rings true with Linux now. Yeah, there are few exceptions here and there, but then again, windows too requires these senslrss Registry settings, or sometimes even command line actions as well

      • @lud@lemm.ee
        link
        fedilink
        3
        edit-2
        5 months ago

        What teo windows admin do in 30 minutes I do in 30 seconds

        You know that pretty much everything in Windows can be done with powershell, right? Just a few and very specific things need to be done using older command line tools, or extremely rarely using a GUI.

        It’s trivial to write a script that changes the DNS configuration on every server for example. It’s even easy to parallelize it.

        You pretty much only need something like this.

        $Servers = “server01”, “server02”, “server03”

        $Servers | ForEach-Object { Invoke-Command -Computername $_ -Scriptblock { Set-DnsClientServerAddress -InterfaceIndex 12 -ServerAddresses (“10.0.0.1”,“10.0.0.2”) }}

        I can’t guarantee that it will run, since I wrote it on my phone (hence formatting), but it wouldn’t be far off. You could also do it without pipes using something like ‘foreach $server in $servers’ but that’s harder to type on a phone and I prefer pipes.

      • NatanoxOP
        link
        fedilink
        English
        55 months ago

        This is just not true. The average Windows user never has to open the registry, only devs and tinkerers have to. Neither a shell.

        For Windows admins do in 30 minutes and you in 30 seconds takes a normal user either 30 minutes ib Linux or, way too often, 30 hours because the random command in the internet didn’t work, did work but had unforeseen consequences (way worse and way too often) or outright broke their system.

        Even KDE lacks settings, and even if they ARE there the community is so god damn “terminalistic” that you’ll barely find the correct answer for the GUI, just a bunch of CLI commands that will age like milk and cause future people who look for help to accidentally break something.

        NOBODY should be forced to enter a superuser command they can’t understand to achieve a goal they very well do. The community is still fighting against the users’ ability to open a file browser or text editor as superuser WITHOUT going through the command line. It sucks, and normal users constantly get alienated by the lack of these fundamental things on a system that pretends to give them full control.

        Full control it does give; after 2 years of painfully learning the command line and its bells and whistles. And this sucks.

        • @Zink@programming.dev
          link
          fedilink
          35 months ago

          I’m sure it’s different in many distros, but in Mint the ability to open a file browser as root is in the right click menu.

    • @renzev@lemmy.world
      link
      fedilink
      English
      04 months ago

      This is such a stupid take. Gui obscures the thing that you want to do behind endless buttons and menus and some bullshit that some self-proclaimed “user experience engineer” thought would be “intuitive”. With cli it’s like you’re talking directly to the computer. Want to stop the networking service? service networking stop. Couldn’t be simpler!

      Also fun fact, Linux has a “wireless devices” tool, command line one and it uses device ID to apply it and the fucking ID changes every time for the device so you can’t make a permanent setting.

      Are you talking about rfkill? Strange, for me the ID’s don’t change. But even if they do for you, what’s stopping you from getting the ID just by grepping for the device name? Something like rfkill list | grep YOUR_DEVICE_NAME | cut -d ':' -f 1 | xargs rfkill block.

      • RejZoR
        link
        fedilink
        English
        04 months ago

        Calls it stupid take, proceeds to give me most absurd noodle of a commandline for something that could simply be a Enable/Disable button on a device list panel that every idiot with no prior knowledge of Linux, CLI or memorized command could do it. I think proved my point once again.

        • @renzev@lemmy.world
          link
          fedilink
          04 months ago

          It would take you less time to put together that one-liner than to find the correct button in an unfamiliar gui. How exactly does that prove your point?

          • RejZoR
            link
            fedilink
            English
            04 months ago

            BS, I looked online for hours and waited for replies on reddit and no one gave me this line. So, no, I’d in fact do it via GUI in minutes where it took me hours for some backwards config that doesn’t look anything like this that made me do what I wanted. With extra steps to copy that stupid file into system folder, of course via stupid Terminal because I couldn’t do it through file manager in any way. The level of stupid Linux has to configure trivial things is just astounding.

            And what’s weird is how Linux purists always whine about it. Like, I don’t care, keep using your stupid Terminal, just give me damn GUI for this basic shit. I don’t want to waste time and memorize idiotic noodles of commands to do trivial shit. No one is taking away any of the stupidity you love, just give ME the choice. Instead the only choice is use of stupid CLI. Ugh.

            Also it’s not “unfamiliar” GUI. It’s called practical deduction. If I need to do this and this I already know I might need to look under this and that category in settings or just type rough related words in search and it would show me the setting. If whoever makes GUI isn’t a complete moron, it would be easy to find. Good luck with any of that with CLI where you need to input exact command from start. Your logic just makes no sense.

            • @renzev@lemmy.world
              link
              fedilink
              14 months ago

              I don’t want to waste time and memorize idiotic noodles of commands to do trivial shit.

              Also it’s not “unfamiliar” GUI. It’s called practical deduction.

              Can you not see how the two arguments you’re making are completely contradictory and self-defeating? Nobody is asking you to memorize “noodles of commands”. What, do you think we all have little books full of shell one-liners for every task imaginable? You just have to know a few basics: The pipe redirects data, cut splits lines of text, xargs builds up arguments raw text, etc. Put them together in whatever way you wish to accomplish the task at hand. It’s – exactly as you say – practical deduction.

              • RejZoR
                link
                fedilink
                English
                14 months ago

                You’re really not making the case in your favor with this argument. So, now I have to memorize even more dumb commands. What in the fuck? You really have no clue about GUI, do you? Youbdon’t have to memorize ANYTHING, just have general idea in which category of settings to go. And that’s it.

  • @stupidcasey@lemmy.world
    link
    fedilink
    135 months ago

    Not entirely accurate since the majority of Linux system settings are in fact GUI settings, you forget the Linux under the hood is all pure text based meaning it’s just GUI settings and worse GUI settings.

    • NatanoxOP
      link
      fedilink
      English
      265 months ago

      Wait, do you argue that a terminal emulator is just another GUI but with a huge text box? 😅

      • @stupidcasey@lemmy.world
        link
        fedilink
        45 months ago

        If we want to be technical even the terminal itself is a GUI just not a very interactive one, technically anything(most things) outside of the grub loader, bios and drives are part of the gui, I will concede that that is not a very useful definition but when dealing with edge cases like terminal emulators you would have to say it is indeed part of the gui at least technically.

        • @highball@lemmy.world
          link
          fedilink
          English
          75 months ago

          It’s called a terminal emulator because it emulates graphically what used to output to a printer at the console of a mainframe. Then you got CRT monitors. The mainframes like the PDP-10 would output to a printer or CRT monitor. This was your terminal. A printer writes the output from the mainframe 1 character at a time, left to right, top to bottom. The CRT monitors were made to do the same. Obviously before outputting to a printer or CRT monitor, the output would show on a set of lights on the console. If you watched them change enough, you would know where you were in your program as it ran (obviously something only doable because the opcodes were not running in parallel through super scalar pipelines in the Ghz). With printers and monitors, you could increase the amount of feedback you get from the running or exiting program and give input to the system via a keyboard.

          So, the terminal is not “technically” a GUI. We do use a GUI to emulate a terminal which receives the actual terminal output from the system and then displays it for you. They are not the same thing at all. GUI is a paradigm for what you display on a Monitor for the user to interact with. Modern monitors are fast enough that they can and do work well with the GUI paradigm. You definitely wouldn’t be sending GUI context to a printer.

          • @stupidcasey@lemmy.world
            link
            fedilink
            7
            edit-2
            5 months ago

            Technically a terminal is a physical crt or phosphate or whatever old kind of monitor they had back then, the dot matrix printer was a tty or teletype system, the terminal emulator is emulating the the old dumb analog monitor on top of the digital os not necessarily the tty although the terminal was doing the same function as the tty, so a raw terminal would be graphical… I guess we are going so far back the words are losing meaning but the terminal emulator which runs on top of the GUI classifies as part of the GUI as much as notepad or word

            • @highball@lemmy.world
              link
              fedilink
              English
              15 months ago

              Look up what makes a GUI. Something can be graphical but not GUI. Something that is GUI is obviously graphical. “All thumbs are fingers, but not all fingers are thumbs”.

        • @highball@lemmy.world
          link
          fedilink
          English
          105 months ago

          So, if I switch the terminal output back to my dot matrix printer instead of my monitor, like back in the day, it’s not graphical right?

      • juipeltje
        link
        fedilink
        45 months ago

        Meanwhile i’m using my own silly bash script to symlink all my dotfiles from my repo 🗿

        • @stetech@lemmy.world
          link
          fedilink
          45 months ago

          Yeah, and then you start to configure any edge case, and then you’re basically already at the point where chezmoi would be useful. Lol, I’ve been there

          • fmstrat
            link
            fedilink
            English
            35 months ago

            Mine uses special folders for ‘all’ or ‘user’, and different folders for symlinking entire folders or single files so the scripts can tell the difference. Had no idea this existed. Thanks!

          • juipeltje
            link
            fedilink
            25 months ago

            Could you give an example of that? Cause i’m kinda curious. I have used home manager before when i was using nixos, but when i left i went back to using my script. It was kinda annoying to me how home manager was much slower.

            • @stetech@lemmy.world
              link
              fedilink
              2
              edit-2
              5 months ago

              Server (Linux) and personal machine (non-Linux Macbook) with the same general shell config (aliases etc.), but different applications/CLI tools installed.

              No idea how it compares against the Nix paradigms, but I like the ease of use in setting up a new machine. It’ll copy all files to their intended destinations and will be able to fill in credentials from templates using e.g. rbw (third-party Bitwarden, i.e. password manager, CLI tool), meaning, once all fields have been templated, you can make it public without even worrying about leaking a personal email address (I use different ones for git vs. other accounts vs. even other stuff).

  • madjo
    link
    fedilink
    45 months ago

    If you don’t know what you’re doing, you have no reason to edit those settings.

    • JackbyDev
      link
      fedilink
      English
      25 months ago

      Conversely, if it was presented in a more user friendly way, perhaps more people would know what they were doing.

  • irelephant [he/him]🍭
    link
    fedilink
    125 months ago

    I think there should be a standard for config files, where it defines all of the options and possible values, so that an app can be made to modify them.

        • @droans@midwest.social
          link
          fedilink
          85 months ago

          There are existing standards. The issue is that there are too many different standards and some programs will choose to make their conf files half standardized, half unique.

          There’s INI, YAML, JSON, XML, TOML, etc.

          Honestly, the Linux team needs to just choose one of these formats, declare it the gold standard, and slowly migrate the config files for most core components over to it. By declaring a standard, you’ll eventually get the developers of most major third-party tools and components to eventually migrate.

          • JackbyDev
            link
            fedilink
            English
            15 months ago

            It’s not about what serialization format, it’s about what possible values there are for each field.

          • irelephant [he/him]🍭
            link
            fedilink
            65 months ago

            Thats not exactly what I meant, I meant a system where you would have a file that defines all the options for an app, and their possible values, so a gui or program could be made to edit them.

            • Ephera
              link
              fedilink
              English
              35 months ago

              What comes sort of close, is that you can define so-called “schemas”, at least for JSON, TOML, YAML and XML. Here’s what that might look like for JSON: https://json-schema.org/learn/getting-started-step-by-step

              I don’t know, if you can actually generate a GUI from such a schema, though. They’re intended for validating existing data, so I don’t know, if they give you enough data to work with to actually provide a GUI. For example, you don’t really have a human-readable name in these. The fields are rather called e.g. “productName”.

              • irelephant [he/him]🍭
                link
                fedilink
                35 months ago

                Yeah, I am aware of schemas, I meant something where you would have, for example, a conf.definition.json file:

                {
                    screenResolution: {
                             definition: "What resolution the screen should be",
                             options: [ 
                                 "1920x1080",
                                  "720x470"
                              ]
                     }
                }
                

                So then, a settings app could control settings for other programs, like apple does, by checking this file, and editing the configuration file based on it.

            • @droans@midwest.social
              link
              fedilink
              25 months ago

              Yeah something like that should be doable but it would require that programs provide a schema and the OS to have a way for the programs to “announce” themselves so it can be aware of the configuration files and the schema.

              I’m sure some project could create a GUI that could cover the most common applications, though.

              It’s always fun trying to set up a program, learning the config syntax, running it, having it fail, and then spending an hour debugging before you realize it never even read your config changes because you were supposed to use one of the other half dozen conf files it has spread all across your drive. Is it under /etc/, /usr/local/etc/, /opt/, or your home directory?

              • irelephant [he/him]🍭
                link
                fedilink
                25 months ago

                I was thinking, they would put the definitions in a specific directory, like if its installed locally, ~/.config/definitions or if installed globally /etc/definitions and then any settings apps would search for those.

    • NatanoxOP
      link
      fedilink
      English
      45 months ago

      Any modern Linux distro viable for the average user uses systemd, and there ain’t many different bootloaders being used by big distros either (almost always either Grub or systemd-boot, rarely Efistub). Likewise it’s clear for years that Wayland is the future (not to mention this problem persists for over 2 decades now).

      I don’t see a problem with lack of standardized config files, rather a lack of interest by the rather tech-conservative part of the Linux community (who by now often have a lot to say in development circles).

    • _donnadie_
      link
      fedilink
      145 months ago

      SUSE/openSUSE are the only ones that have it figured out. It requires a lot of polish, but it’s the only distro that seems to really care about a deeper system configuration through GUI, and that’s really appreciated.

      • @paequ2@lemmy.today
        link
        fedilink
        English
        21
        edit-2
        5 months ago

        Yeah, I’ve definitely grown to like TOML, especially after spending hours trying to edit a giant (nested) YAML file…

        I didn’t realize the indentation in TOML was purely aesthetic.

        This

        [servers]
          [servers.alpha]
          ip = "10.0.0.1"
          dc = "eqdc10"
        
          [servers.beta]
          ip = "10.0.0.2"
          dc = "eqdc10"
        

        equals this

        [servers]
        [servers.alpha]
        ip = "10.0.0.1"
        dc = "eqdc10"
        
        [servers.beta]
        ip = "10.0.0.2"
        dc = "eqdc10"
        

        which equals this

        {
          "servers": {
            "alpha": {
              "ip": "10.0.0.1",
              "dc": "eqdc10"
            },
            "beta": {
              "ip": "10.0.0.2",
              "dc": "eqdc10"
            }
          }
        }
        
        • Fushuan [he/him]
          link
          fedilink
          English
          55 months ago

          Once the file is big enough wouldn’t it be better to convert it to json before editing, then converting it back?

          Let the computer deal with indents and all that stuff.

          • Ephera
            link
            fedilink
            English
            35 months ago

            I love this comment. JSON is by far the format that cares the least about being human-readable or -writable, but you’re seriously proposing writing it rather than YAML. And I kind of don’t even really disagree. But a big problem with that strategy is that you won’t find documentation for how to write the configuration in JSON.

            • Fushuan [he/him]
              link
              fedilink
              English
              2
              edit-2
              5 months ago

              I disagree that json is not human writable. JSON is perfectly writable since it has explicit visible separations between elements.

              It might look ugly but it’s perfectly readable and writeable.

              Granted, I always read json after parsing it with an auto formatter. Maybe that’s why people say that json is difficult to read? It’s true that unformatted json (minified) is way worse than yaml but no one in their right mind would not format the json, specially when it’s natively supported by most code editors.

              BTW, about documentation, post formatting json looks very much like a yaml, all yaml docs can be converted to json instructions if you think a little bit.

              • Ephera
                link
                fedilink
                English
                15 months ago

                Oh, that is actually the part I do agree with. I don’t think everyone will, but I do actually think JSON is easier to read and write (correctly) than YAML. I specifically wrote that JSON cares the least about that, because it was designed to just serialize JavaScript objects into strings and back. As far as its original purpose is concerned, no one would ever need to hand-edit JSON. Which is also why it doesn’t support comments (which is still somewhat of a dealbreaker for a configuration language, although I guess for your proposed workaround, one could potentially use a JSON flavor which supports comments; potentially, you can even write your JSON in the YAML file with comments directly and then not convert it, since YAML is a superset of JSON).

                As for documentation, yeah, it is possible to convert, but it makes it more annoying, particularly also if you then can’t easily re-use configs in another project. And if you’re working in a team, having to explain to all your team members, how they can convert the official documentation, is also not really acceptable…

          • @paequ2@lemmy.today
            link
            fedilink
            English
            15 months ago

            Because … well … wait, not a bad idea. Although, this would get rid of comments. Which in my case, I didn’t have too many, so I could have manually added them back.

  • @SpikesOtherDog@ani.social
    link
    fedilink
    87
    edit-2
    5 months ago

    What people expect:

    ✅Fix my box

    ❎Fuck my shit up

    What we would get: System Kernel Interface

    🔳 Regex Recursion

    🔳 Kernel Language (Internal) [Dropdown: en-us, Dvorak, binary, Klingon, non-binary (Borg analog), Esperanto]

    🔳 Ignore LPT on fire

    🔳 Memory hole on sysctl

    🔳 Mansplain man(8)

    • @Oinks@lemmy.blahaj.zone
      link
      fedilink
      14 months ago

      Yeah some people seem to have this expectation that there should just magically be a button to unbreak the PC. They talk about their personal pain points when using Linux as if there’s a conspiracy of devs to hide the unbreak buttons for the sake of elitism, but that… just isn’t a thing? If it was that easy to fix an issue, you probably wouldn’t need to fix it because the system would already come unbroken by default. I sympathize with everyone’s Bluetooth configuration woes but mostly it’s a pain in the ass because Bluetooth, in general, is a pain in the ass, not because of elitist devs (who I should mention are doing this in their free time for no pay. There’s almost no money in desktop Linux, unlike in servers).

  • TimeSquirrel
    link
    fedilink
    135 months ago

    The janky cobbled-together UIs straight out of 1994 are part of the charm!

  • @smiletolerantly@awful.systems
    link
    fedilink
    24 months ago

    Is this some peasant meme I am too NixOS to understand?

    (Joking, joking. A good system settings center is important for graphically managed distros.)

  • @Daerun@lemmy.world
    link
    fedilink
    94 months ago

    I’ve been using linix for like 18 years and I still prefer GUI over CLI hands down. Make things easy by letting me click on some nicely explained buttons.