Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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.
Let the apologists have a field day in the comments.
I'd just like one standard for all config files. Yaml, json, whatever...let's just choose something and standardize.
I used to dislike editing text config files but once you have one written you've got a template for the future. So long as the documentation is throughly written it's not too bad to follow.
Nix intensifies
Since suggestions in the comments are just words of apologists, do you have a proposal for a solution, or is this just a rant post?
All Iโm getting right now is a vague idea of some Master GUI that resembles the cockpit of a commercial jet that no โaverage userโ is ever going to try and decipher, anyway.
reminds me of the one time I tried to configure a proxy on fedora KDE and then realizing most apps don't even use the inbuilt proxy settings and there are three separate ways to configure it that are only accessable via the terminal and it is pain
You ever try to put together a GUI? I absolutely get why they look like crap! Although I have been having fun playing around with egui.
NixOS has the potential to do really well here. The Nix language has a rich enough type system to generate GUI forms for every field, and there are several projects being worked on that allow editing NixOS options from a GUI. They're still very janky, but it's definitely possible to get to a point where a layperson could operate them without breaking their system.
Here's one:
Audio jacks. I have a 5.1 system, and to use it properly I have to install HDAJackRetask. You can't just specify 5.1 surround sound from the distro's standard audio settings menu.
Desktop Environments are decoupled from the underlying system. It makes switching DEs very easy but integration sucks.
I needed to flush dns on my Ubuntu machine. I googled it found a command for an older version. But of course the underlying stuff changed since then and that command doesn't exist anymore.
The command to flush dns on Windows has been the same for decades. On Linux half the stuff I learn is going to be obsolete in a couple of years and that knowledge can't be carried over to other Distros because they do it differently.
I also had to manually build and install a driver for a very common realtek wifi chipset that is not even new.
Is this some peasant meme I am too NixOS to understand?
(Joking, joking. A good system settings center is important for graphically managed distros.)
The janky cobbled-together UIs straight out of 1994 are part of the charm!