Submitted by Windows might be a popular platform for running certain kinds of Web applications. But too many developers have been burnt by trying to deploy PHP applications on a Windows server. “If you banged on [a PHP application] too hard on Windows, IIS would crash, and nobody could tell why it died,” Microsoft’s Garrett Serack says. Microsoft is aiming to change that. In fact, while you weren’t looking, they already made some improvements.
Apparently it is IIS that is crashing, not Windows. Thus wouldn’t using Apache on Windows also solve this problem? Apache does run on Windows. Is it that nobody bothers to run Apache on Windows?
RTFA, they barely talked about IIS, more about the build process for windows, and the external libraries used.
Nevermind.
Edited 2009-07-30 19:53 UTC
What does that statement have to do with the question he asked? Nothing.
Yes, PHP runs happily on Apache for Windows. No need to use IIS, unless your company is a Microsoft partner/Microsoft certified org/Windows certified or whatever – then you’re probably tied to IIS to keep the accreditation (guessing – correct me if I am wrong.)
Why was he asking questions about iis when it was only mentioned once in a two page article about improving the performance of php on windows?
Because apparently it’s a problem with running PHP with IIS, not running PHP on Windows per se. You don’t have to use IIS as the webserver under Windows, unless you need ASP and the like.
Because what they mean by running PHP on ‘Windows’ is clearly Windows + IIS. If you run PHP on Windows under Apache then most, if not all, of those issues disappear. Thus, running PHP on Windows is not a problem at all. They just chose to ignore the most obvious solution.
Edited 2009-08-01 23:26 UTC
They threw money at it. Or Chairs.