Linked by Thom Holwerda on Wed 4th Oct 2006 12:43 UTC, submitted by anonymous
Linux "George Weiss, Gartner's open-source analyst, recently said that Microsoft Windows will not suffer irreparable damage on the server side at the hands of Linux over the next five years. He's right. Microsoft will fall flat on its face all by itself, and Linux will pick up afterwards. It's very simple."
Permalink for comment 168265
To read all comments associated with this story, please click here.
RE: It's very simple
by naelurec on Wed 4th Oct 2006 15:48 UTC in reply to "It's very simple"
naelurec
Member since:
2006-02-15

I will disagree with you. The shell on Linux is your scripting language. So the same exact commands and processes you use on a day-to-day basis, you can easily throw into a script. With Windows, the GUI you master is not easily scriptable -- you need to learn a completely different process to script the system.

On *nix, it is trivial to confiugre hundreds or thousands of similar servers due to the ability to copy and paste text-based configuration files and use standard search and replace techniques to adjust as necessary (ie IP addresses, system names, etc). In addition, tapping into SSH makes it a breeze to do this automatically and over a secure channel.

Then there is the resource benefit -- a GUI takes up more system resources and has much more overhead .. so a significant portion of a lower powered system is required for non-essential processes (GUI).

With *nix, it is rather easy to determine what configuration changes took place (those are the only ones in the config file). With Windows, some options might be enabled by default -- but by looking at the GUI, you are unaware which options are enabled by default and where were customized. In addition, in a well maintained network, versioning is inplace to allow an administrator to go back-in-time to see changes to a config (and even who made changes and why) .. with Windows, not so much.. when something breaks, unless your writing down changes elsewhere in a consistent manner, your troubleshooting is significantly more guesswork than analytical.

I find that due to the relative ease of getting a cookie-cutter Windows server up and going (as per your screenshot) that this has fostered many self proclaimed "gurus" that ultimately cause a significant amount of harm to their customers due to poorly configured and secured networks. Perhaps initial ease of use in setup is NOT a good metric for an administrator. I'll be honest with you -- I almost think that some of the overly long and cryptic commands of *nix forces an admin to be more efficient by scripting and automating their systems.

Reply Parent Score: 5