Slashdot Mirror


Windows 2003 takes 5% away from Linux

ZuperDee writes "According to Netcraft, the number of Windows 2003 servers has doubled since July, and 5% were running Linux before, which is consistent with the trends they've been observing for some time. This doesn't look good for Linux, in my opinion. Maybe we should all start to think about jumping ship?"

2 of 873 comments (clear)

  1. Re:Doh. by Karamchand · · Score: 5, Interesting
    Certainly one can interpret - or at least phrase - it in many different ways. Some important questions:
    • What about those 5%? What did they dislike about Linux, why did they switch (back?) to Windows? - We need to get in touch with folks who switched from Linux to Windows and ask them these questions.
    • What about these other 95%? Why didn't they switch to Linux instead of switchting to the - probably much more expensive - Windows 2003? What features is Linux missing Windows 2003 can offer?
  2. Re:Doh. by Karl+Cocknozzle · · Score: 5, Interesting
    Certainly one can interpret - or at least phrase - it in many different ways. Some important questions:

    What about those 5%? What did they dislike about Linux, why did they switch (back?) to Windows? - We need to get in touch with folks who switched from Linux to Windows and ask them these questions.

    In our case, we switched our Samba servers over to Windows 2000 about 18 months ago because a new CIO was installed, and he commanded from the ivory tower that we would be all Microsoft within one year from his start date. No, we aren't using 2003--yet. But it seems conceivable to me that other companies are in similar situations... Their linux machines run great, like toy cars on Christmas morning, but somebody somewhere in authority gets a pitch from an MS salesman, and the next thing you know, bye-bye Samba and Apache, hello IIS and Windows 2003 file servers. (Ugh!)

    So in our case, it was an arbitrary decision by somebody higher up. We never had ANY problems with the Samba servers, but because he used to work at Microsoft (in Redmond, y'all!) it was done.

    Or perhaps they decided they wanted to re-write their whole web-site in ASP.net. I know a job I applied for recently was mine until we started talking about their web-site, and I recommended they not go ASP but implement their new site in HTML/PHP on apache using a low-cost database like mysql or postgres. As a one-man band, I would prefer to spend my time patching the parts of apache/php/mysql that need patched, rather than having to test and verify the twice per afternoon stuff that has been out from MS lately.
    --
    Who did what now?