I fully agree. GUI and servers have nothing to do with each other. I am all for GUI "control panels" for the normal home user, as Linux will not succeed if the normal user is not able to change some settings in their own computers.
As a server administrator I would hate GUI for servers. Instead I use a combination of scripting, salt-stack and direct ssh contact. Lets take this trivial case: In the fall when the schools begin, I end up creating user accounts for every single new student. I receive name lists. Those list I format into the way I want (sed/vim). Then I run the lists trough a script I made which will create random password, make their home directories and set up everything right for them. Out I get a csv file containing their usernames and passwords. That csv file I can use in any office application. How do you do that efficiently by GUI?
It is not a coincidence PowerShell appeared in Windows. Any administrator not able to script is pretty much a worthless administrator. A such person is wasting time (=money) by doing over and over the same task. Mistakes will creep in here and there as with any repeated task.
Another case: Lets say a service has hung. Now I am able even with my phone and a simple ssh client to take remote connection and restart the service. As soon you have GUI and VNC/RDP/Whatever GUI you need more bandwith and working over a slow mobile connection might be almost impossible. Take then screen size also into account.
As a server administrator I would hate GUI for servers. Instead I use a combination of scripting, salt-stack and direct ssh contact. Lets take this trivial case: In the fall when the schools begin, I end up creating user accounts for every single new student. I receive name lists. Those list I format into the way I want (sed/vim). Then I run the lists trough a script I made which will create random password, make their home directories and set up everything right for them. Out I get a csv file containing their usernames and passwords. That csv file I can use in any office application. How do you do that efficiently by GUI?
It is not a coincidence PowerShell appeared in Windows. Any administrator not able to script is pretty much a worthless administrator. A such person is wasting time (=money) by doing over and over the same task. Mistakes will creep in here and there as with any repeated task.
Another case: Lets say a service has hung. Now I am able even with my phone and a simple ssh client to take remote connection and restart the service. As soon you have GUI and VNC/RDP/Whatever GUI you need more bandwith and working over a slow mobile connection might be almost impossible. Take then screen size also into account.