you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 2 years ago* (last edited 2 years ago) (4 children)

Linux lacks GUI configuration tools for many things, you have to edit text files often using guidance for obsolete versions of software and hope it works. Every single config file can have thousands of lines and if you wrote something wrong it will crash or start acting weirdly, very fragile design. GUI config tools mostly allow valid inputs like checkbox true/false and complain if the path isn't valid.

Edit: to clarify, i'm exclusively using linux since 2008 and i'm not 'afraid of editing config files', downvoting me doesn't fix the problem. I'm also not fond of fixing your header files for them to compile.

  • source
  • hideshow 8 child comments
  • [–] 4 points 2 years ago

    These things exist for windows as well but they are not accessible. Linux is a car without the plastic hood over the motor. Its not dumbed down.

    Does that make it hard to see the three things a noob should touch? Yes.

    But there are linux distros that take care of this so this comment isn’t correct.

  • source
  • parent
  • [–] 3 points 2 years ago

    SUSE is weird but their YaST was compelling enough to make them an option. Cockpit in RHEL doesn’t compare. I think that having admins edit text files is bad. The capability should be there, but it should not be mandatory. Editing files manually instead of a GUI increases the odds of a mistype trashing the system.

  • source
  • parent
  • [–] 2 points 2 years ago

    There's loads of windows configuration files with options in them that the GUI for it's software isn't showing you. That's just a matter of developer choice. I gotta open a config to get Morrowind to play at higher resolution for example.

  • source
  • parent