Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: phranque
My whole philosophy is and has been that ms is a US-centric technology and there is no real motivation for the rest of the world to enrich Bill with his licensing fees when there are other alternatives that are open source and in most cases better products to do the job.
The web is an international market and to limit yourself by using ms-centric software is what I believe will be an unnecessary hindrance on down the road when we usher in a truly global commerce system.
Yep, sounds correct to me.
"The survey shows 49% of the computers running the web are Windows based; a little more than all of the Unix-like operating systems combined....Although Apache running on various Unix systems runs more sites than Windows, Apache is heavily deployed at hosting companies and ISPs who strive to run as many sites as possible on a single computer to save costs. Windows is most popular with end-user and self hosted sites, where the host to computer ratio is much smaller."
The gragh [netcraft.com] shows it best.
He also says it's easier to find qualified support personnel to manage Unix servers.
That is a point I hadn't thought about, but I could see how that would be the case.
It is difficult to find someone who *really* knows their stuff with an MS server. The people who are really good with Unix have been in unix a long time, and consequently, the operating system(s) -- whichever one you specialize in -- have not changed dramatically over the last 10 years.
ls -l still means "show me the list in a long form" just like it did 10 years ago.
With MS, there hasn't been that continunity, so it is more difficult to find someone who is really experienced with it.
Now, when you do find someone who is really good in an MS environment, they are usually *really* sharp. They'd have to be to pick up all that in such a short period of time.
Case in point, I have a client who has a dedicated Win2000 box. They have two full time tech guys. The server was spitting out double header information when a perl script was called via ssi. I hassled them for weeks to fix it, but then I realized they had no clue. So I did some poking around, and held their hands as they made a mapping adjustment. The irony of the situation was that I have never touched IIS, win2000,or NT. I just know how to poke around on the web a bit. I showed them the info I found, but that wasn't enough, I had to interpret it for them.
I know it sounds made up, but this really did happen.