3 ms·

> Setting up a scheduled job http://corntab.com http://corntab.com https://github.com/alseambusher/crontab-ui https://github.com/alseambusher/crontab-ui > Man

> Setting up a scheduled job http://corntab.com http://corntab.com https://github.com/alseambusher/crontab-ui https://github.com/alseambusher/crontab-ui > Manipulate the firewall http://gufw.org http://gufw.org > Configuring a website http://apachegui.net http://apachegui.net (How can you do it in gui on windows?) > Changing permissions on a .py file to execute it Any normal file manager, i.e. thunar. > I don't include third party packages as "UI" Why? They're not hard to install if you need it.

cm2187 10y ago
> How can you do it in gui on windows? IIS has a UI for pretty much everything > Why? They're not hard to install if you need it. Yes but 1. pretty much everyone uses txt commands so configuring these things with a UI would typically not appear in search results when looking for how to do something 2. having a UI is about making the OS self discoverable and intuitive. If it takes to be aware of and install some third party packages then the UI failed its objective. Another thing that often tripped me in linux is the variety of distributions and tools to do the same thing. I can understand why advanced users appreciate having the choice, but from a beginner point of view, it makes it quite hard as the syntax that will work on one distribution of linux or with one tool will break another.
- vetinari 10y ago
  > IIS has a UI for pretty much everything And it was game of "where they did hide that thing I need to configure right now?" at the beginning. Fortunately, later they did allow config files. Additionally, GUI does not allow all the thing you can (and want) to configure using the config file. You can also put your config files into svn or git repository and track changes to them over time. No more "what did I set to that server two years ago?" moments. You can also recycle config from one server to another, without clicking all the days. So as a beginner, do not get used to GUI applets. Later, you will be thankful you didn't.
  - digi_owl 10y ago
    > And it was game of "where they did hide that thing I need to configure right now?" And sadly that is a game that the Linux user space devs are getting very adept at implementing...

cm2187 10y ago

> How can you do it in gui on windows? IIS has a UI for pretty much everything > Why? They're not hard to install if you need it. Yes but 1. pretty much everyone uses txt commands so configuring these things with a UI would typically not appear in search results when looking for how to do something 2. having a UI is about making the OS self discoverable and intuitive. If it takes to be aware of and install some third party packages then the UI failed its objective. Another thing that often tripped me in linux is the variety of distributions and tools to do the same thing. I can understand why advanced users appreciate having the choice, but from a beginner point of view, it makes it quite hard as the syntax that will work on one distribution of linux or with one tool will break another.

vetinari 10y ago
> IIS has a UI for pretty much everything And it was game of "where they did hide that thing I need to configure right now?" at the beginning. Fortunately, later they did allow config files. Additionally, GUI does not allow all the thing you can (and want) to configure using the config file. You can also put your config files into svn or git repository and track changes to them over time. No more "what did I set to that server two years ago?" moments. You can also recycle config from one server to another, without clicking all the days. So as a beginner, do not get used to GUI applets. Later, you will be thankful you didn't.
- digi_owl 10y ago
  > And it was game of "where they did hide that thing I need to configure right now?" And sadly that is a game that the Linux user space devs are getting very adept at implementing...