Hi everyone,
Well, it looks like Microsoft came out with the new Windows Home Server. It's based off of Windows Server 2003. Finally there is an OS with a fully functional, unrestricted IIS service that's priced close to XP-Pro and Vista, around $180 to $200.
Then there is Pablo's Q-n-E web server that costs around $40 or $50 bucks and can run on of any Windows operating system.
Then there is Linux (free) with PHP (free) and Apache (free) that can run on a linux, unix, sun or Windows box.
I am pretty fed-up with Gates and Microsoft, making the unrestricted IIS service exclusive only to Windows Server operating systems for about 10 years now. Because of this choice, a very good percentage of the consumer, IT and developement population chose to use either Linux with Apache web server and PHP support, or load PHP and Apache (or some other web server software) on windows boxes, because that was the only alternative for having an inexpensive web server at home or in a small business without paying an arm and a leg and your first born for a Windows Server box. Not to mention most of the web hosting companies offering to host sites on Linux or Unix boxes with Apache and usually at a cost less than hosting on a Windows box.
I've used Pablo's Q-n-E server on and off for a little over 2 years now. It's simple, user friendly, intuitive, affordable ---yet not all ASP scripts that were coded and tested in IIS work with it. Yet, the Q-n-E web server is the only affordable ASP friendly alternative to IIS.
So here is my question. Would it be at all possible for ASP script developers, like WWG, to be willing to code ASP products that are Q-n-E friendly?
I know IIS service in windows servers, being the only platform that functionally hosts ASP, has become the only defacto functional standard to code by, yet it is because of this reason PHP scripts have become so popular and functional on any box with PHP.
With the recent introduction of Windows Home Server to the home consumer market, a small part of me wants to flip Bill the birdy and say "too little, too late, (type expletive here)".
From a cost benefit standpoint, I can see how one can reason that coding for IIS is more profitable because people willing to and able to afford a windows server would also most likely be willing to afford and pay for your ASP products.
At the same time, IIS, ASP and ASP.NET has always lagged behind Apache/PHP in market share, because Bill was and still is a (type expletive here). Therefore, wouldn't coding scripts compatible with both IIS and Q-n-E somehow, sort of level the playing field as well as expand the niche market you are trying to sell your products to?