Linux ist mostly used for servers, where you rarely need/have a graphical environment. A big part of development is making sure to keep the kernel safe and prevent endangering critical infrastructure.

That said, I agree if Linux is to be adopted more widely as a desktop system, good graphical UI is crucial. It’s just not the focus of most Linux devs.

If you want a gui, pick pop os, linux mint, etc. If you really like the arch package managers, install something like the KDE or GNOME flavors of endeavour or garuda. Stop deliberately choosing a terminal heavy distro.

You get the GUI you pay for unfortunately.

Feel free to open a pr.

I’m fine with config files, as long as they are where you expect them (~/.config/tool or ~/.tool). What I dislike is yet another funny config syntax because the dev couldn’t settle on an established standard. Command line syntax is ok, if you give me sensible completions.

I used to wish for GUIs, but at some point all the textual config clicked and I am now actively avoiding GUI. It’s only intuitive for simple toggles and is usually a lot more limited with complex config requirements.

I agree that having better GUI is a generally good thing and that most of us would benefit from it. However it’s false to state or believe that Linux in its totality is bereft of this. Distros like openSUSE, MX Linux and Garuda Linux have put in considerable effort into offering tools that enable one to config a lot of stuff through a GUI. However, it doesn’t make a lot of sense to complain about the lack of GUIs if you (or whosoever for that matter) don’t use one of these distros. Arch has minimalism as one of its design goals, so you either have to find the binaries/apps/packages (or whatsoever) that allow you to config through a GUI or you’re out of luck.

What does GTFO mean in this context exactly?

Your issue seems less the command line and that things aren’t “working”, or the tools you want aren’t pre-packaged.

Using Arch Linux was not the best idea if you want something that “just works”, as it works on a philosophy where you install the minimum amount required and then add things, such as drivers or packages, as you need them. In other words, it’s a distribution where you know what you need for your system. It is also a command-line centric distribution, so it’s strange that “GUI” is your bug bear when you picked one that deliberately forces command line.

Regarding overclocking and GPU configuration, you just get CoreCtrl, which even has a GUI.

Now don’t get me wrong, I absolutely agree that everything should have a user interface as much as possible, but the whole “Linux means you have to use command line all the time!!” is simply just not true anymore, and I feel this issue comes from people recalling memories from 10 years ago or using distributions where command line is necessary, rather than something like Ubuntu or Linux Mint where it mostly isn’t.

https://gitlab.com/corectrl/corectrl

CoreCtrl is a Free and Open Source GNU/Linux application that allows you to control with ease your computer hardware using application profiles. It aims to be flexible, comfortable and accessible to regular users.

• PowerUPP: GUI functional AMD GPU configurator for all voltage configuration, frequency tuning, SoC and memory frequency and voltage tuning

• CoreCtrl: GUI usually-functional AMD GPU configurator. Fan curves, over and under clocking, power profiles, frequency and voltage tuning

You have to enable ‘amd.ppfeaturemask=0xffffffff’ in your boot options, but that is clearly stated in the user guide.

For sound, PAVUcontrol or the KDE volume setting GUI have been able to fix 80%-90% of my audio issues. I haven’t used a command line for audio in a long time.

I agree that GUIs make it easier for mass-adoption but things not working out of the box and having to search for solution is just as much of a Windows problem as Linux. If someone has non-standard hardware, it is always a bigger problem to switch to another system. Windows still will randomly shut off my Yeti microphone input and switch to my monitor with no microphone as the system microphone on boot sometimes.

The difference is in windows for weird setups you have to run obscure possible virus runme.msi from 2015 where linux you have to put in an obscure command that you aren’t sure what it does from a forum post from 2015. The only one that has mostly nailed that down is OSX.

deleted by creator

You can always create a GUI yourself, if you think it’s so simple. It would be greatly appreciated and giving back to the community would be nice.

There’s a difference between complaining and providing constructive feedback. This post falls in the former category. If you are a user of a free product and you don’t like how it works, you are entitled to a full, no questions asked, refund. You’re welcome to make suggestions but devs who work hard to provide something at no cost and on their own time owe nobody anything. I’ve seen this play out year after year in the open source community and it’s led to a lot of very good projects shutting down when the developer gets fed up with the demands and behavior of the community of users.

“Be the change you want to see in the world.”

But anything that requires configuration…should have a fully functional GUI.

Does this apply to ones with only 4 or 5 options to configure, where’s the cutoff? Configuration files set the default flags and arguments, and a lot of command line tools that are configurable are small and simple enough that making a GUI just to configure it is not worth the hassle, the increased complexity and codebase size. The idea is that if the software is one or a few executable binar(ies) with enough flexibility, then contributors who’s proficient with GUI toolkits can write the GUI wrapper (as a separate package), otherwise it’s actually just a waste of time for the main dev(s). If that sounds reasonable, then you could write it yourself, pay someone to do it, or wait for someone to volunteer their time.

To address the problem itself. Maybe you should explain what problems you have with editing the configuration files yourself? I know the cons are: (1) having to know or be able to read toml, yaml, json, ini, or some kind of config syntax (but I think they are designed to be generally quite easy to understand), (2) it takes a bit longer to find and open if you’re not used to it, (3) everything is a file so it’s linear, making it harder to see where things are, so longer configs are a PITA. Good tools I think benefit from a GUI or TUI is TLP, archive managers, calculators, volume controllers, font manager or viewer (kinda obvious), why would you want a GUI to configure, e.g., bat, pacman, i3, dunst, all the xorg stuff like xresources, xmodmap??

In return, the pros are: (1) if there are no external docs, the docs can stay inside the default or sample configuration in the form of comments, whereas for GUI you can’t possible include this information for every single toggle, (2) it’s harder to version control because of increased abstraction, (3) it’s not possible to translate every configuration field to a GUI if it’s beyond just a toggle, you would still have to type things in.

I think having an extra GUI wrapper is a matter of complex balance, and made into reality by contributors and volunteers (or eventually, the devs themselves). To say everything should have a FULLY functional GUI if you have to configure it is a bit of an exaggeration and overreach.