Extra vids for Floaties! https://www.floatplane.com/channel/TheTrashNetwork/home
Car Channel: https://www.youtube.com/channel/UCHdpnvKJDijKNe2caIasnww
Game Channel: https://www.youtube.com/@HelloImGaming
Drum Channel: https://www.youtube.com/@the.drum.thing.
To be honest, a lot of system configuration is better done on the CLI or editing configuration files manually (see the majority of the audio stack). I like that approach way more than Windows but even the System Registry in Windows is more “GUI-like” than editing ALSA files or pam.d files manually (usually on the cli as they mostly require sudo). This scares people.
You want the most common things available in a Settings app(s) as they generally are on Gnome, KDE, Windows and Mac. If we cram too much stuff in there regular people struggle. Finding a good balance is a dilemma for most platforms. You want the less obvious stuff to be available in additional specialist “tweak” apps for more experienced users as they often are on all these platforms but sometimes less so on Linux. Then the really esoteric stuff you have to edit registry settings, conf files and plists as you do on all of them. Linux tends to provide more power and flexibility but requires reading documentation due to the diversity of config methods and locations.
A Mac user very sensibly contacted me worried about pasting a command to edit a plist into the terminal from a website they found trying to fix an issue. Nobody should be pasting commands they don’t understand into terminals. A quick search and I found the GUI toggle to do the same thing. It isn’t exclusively a Linux issue. Windows and Mac have complex operating systems underneath and equivalently powerful command line tools.
GUI config isn’t practical for hardcore linux users. It isn’t scriptable, we can’t store it in version control, it is harder to document, it is harder to use remotely. We have to appreciate that we have a growing number of users where it is worth taking a bit more time and sharing an alternative if one exists. However nobody wants to configure services in a GUI as we want to version, document and distribute this stuff and managing services in a GUI is unprofessional because you lose these things.
To be honest, a lot of system configuration is better done on the CLI or editing configuration files manually (see the majority of the audio stack). I like that approach way more than Windows but even the System Registry in Windows is more “GUI-like” than editing ALSA files or pam.d files manually (usually on the cli as they mostly require sudo). This scares people.
You want the most common things available in a Settings app(s) as they generally are on Gnome, KDE, Windows and Mac. If we cram too much stuff in there regular people struggle. Finding a good balance is a dilemma for most platforms. You want the less obvious stuff to be available in additional specialist “tweak” apps for more experienced users as they often are on all these platforms but sometimes less so on Linux. Then the really esoteric stuff you have to edit registry settings, conf files and plists as you do on all of them. Linux tends to provide more power and flexibility but requires reading documentation due to the diversity of config methods and locations.
A Mac user very sensibly contacted me worried about pasting a command to edit a plist into the terminal from a website they found trying to fix an issue. Nobody should be pasting commands they don’t understand into terminals. A quick search and I found the GUI toggle to do the same thing. It isn’t exclusively a Linux issue. Windows and Mac have complex operating systems underneath and equivalently powerful command line tools.
GUI config isn’t practical for hardcore linux users. It isn’t scriptable, we can’t store it in version control, it is harder to document, it is harder to use remotely. We have to appreciate that we have a growing number of users where it is worth taking a bit more time and sharing an alternative if one exists. However nobody wants to configure services in a GUI as we want to version, document and distribute this stuff and managing services in a GUI is unprofessional because you lose these things.