5 ms·
GUIs might be easy to use (e.g: IIS manager), but when you have to manage 50 machines, programability is important and automation becomes more important.
by partycoder 9y ago
GUIs might be easy to use (e.g: IIS manager), but when you have to manage 50 machines, programability is important and automation becomes more important.
- 1_2__4 9y agoYeah anytime someone says GUIs are “easier” my question is always “for what?”. Not because a CLI is always (or even usually, depending on how you slice it) superior, but because a GUI makes some things better and some things a lot worse. So many use cases are not “easier”, they’re harder.
- digi_owl 9y agoAnd why, after so many years, MS introduced Powershell. Now you can do a GUI-less Windows server install, as manage it completely over the CLI. Never mind that with Windows 10 there is no damned way to tell Windows to request a new address from DHCP if the initial attempt failed. The only way to do so is via the CLI and ipconfig.
- partycoder 9y agoPowershell is fine. However the Windows philosophy is different. In Unix, "everything is a file", and what is not a file, is a program that can be configured or a CLI with arguments that can be passed in programatically.