Comment Re:Read Microsoft's page ... (Score 1) 660
Okay, so I went over the top with the finger one.. that's what a case of beer will do to one while reading these things :) Note to anyone who questions why I have so many Win boxes - I am a home-based developer for a MS-centric company.
My primary dev Win2K server - SQL 7.0, IIS 5.0, InterDev, and all current patches.. In order to follow the MS philosophy on these things - doing it the "suggested" way - creates accounts out the wazoo that then have to be deciphered and applied in the right places. Usually there are multiple places and missing any one of those will cause a failure - seldom with useful error messages. I've been doing admin on NT and Win2K servers for 5 years now and it never fails to amaze me how complicated MS seems to make simple things.
RE: SQL Server - sure, it can use Windows authentication. However if one wishes to write code/script that is not hostage to MS' ever-changing standards? In that scenario I would rather USE the standard SQL logon that can be changed simply and easily in one's scripts - not a bastardized MS scheme requiring one to go change user accounts, groups, etc. In SQL Server setups, the MS path is to create all NT based authentication.
Blue screens - In previous versions of Windows - the 9* and ME series - BSOD was more common. My primary dev server is the most frequent BSODer. And yes, it is configurable to either sit at BSOD, or dump and reboot. Mine dumps/reboots. However, more common these days is the complete lockup - requiring an unfriendly power off that risks disk corruption. Losing Konqueror and having to click up another instance is much different than losing everything that may be open on a Win box. My experience now has been that shutting down X will most frequently solve ANY lockup problem without risk of disk corruption. Granted if you have apps up you will lose that data - but at least you don't have to wait for a reboot that adds only insult to injury.
Builtin BASH - "Builtin" (if that's a word) is the key word here. I *don't* want to actually use it under Win - and yes, WSH is great. I have used it for several time-saving little utility apps that don't really need to be full-blown apps. But for a company to create a bunch of crap and point their finger saying "See the other guys don't have THIS!" is ludicrous.
Finger - Uh, yeah went over the top here - It does. My apologies.
That all said - I use both OS types. I make my money on the MS OS and apps and will always be partial to them... but for my OWN use? Linux. Documentation may lag, but for simplicity, security, stability, and above all, STANDARDS, I would rather have a Linux box in front of me any day.
My primary dev Win2K server - SQL 7.0, IIS 5.0, InterDev, and all current patches.. In order to follow the MS philosophy on these things - doing it the "suggested" way - creates accounts out the wazoo that then have to be deciphered and applied in the right places. Usually there are multiple places and missing any one of those will cause a failure - seldom with useful error messages. I've been doing admin on NT and Win2K servers for 5 years now and it never fails to amaze me how complicated MS seems to make simple things.
RE: SQL Server - sure, it can use Windows authentication. However if one wishes to write code/script that is not hostage to MS' ever-changing standards? In that scenario I would rather USE the standard SQL logon that can be changed simply and easily in one's scripts - not a bastardized MS scheme requiring one to go change user accounts, groups, etc. In SQL Server setups, the MS path is to create all NT based authentication.
Blue screens - In previous versions of Windows - the 9* and ME series - BSOD was more common. My primary dev server is the most frequent BSODer. And yes, it is configurable to either sit at BSOD, or dump and reboot. Mine dumps/reboots. However, more common these days is the complete lockup - requiring an unfriendly power off that risks disk corruption. Losing Konqueror and having to click up another instance is much different than losing everything that may be open on a Win box. My experience now has been that shutting down X will most frequently solve ANY lockup problem without risk of disk corruption. Granted if you have apps up you will lose that data - but at least you don't have to wait for a reboot that adds only insult to injury.
Builtin BASH - "Builtin" (if that's a word) is the key word here. I *don't* want to actually use it under Win - and yes, WSH is great. I have used it for several time-saving little utility apps that don't really need to be full-blown apps. But for a company to create a bunch of crap and point their finger saying "See the other guys don't have THIS!" is ludicrous.
Finger - Uh, yeah went over the top here - It does. My apologies.
That all said - I use both OS types. I make my money on the MS OS and apps and will always be partial to them... but for my OWN use? Linux. Documentation may lag, but for simplicity, security, stability, and above all, STANDARDS, I would rather have a Linux box in front of me any day.
