Linked by Thom Holwerda on Thu 30th Jul 2009 16:06 UTC, submitted by estherschindler
Post a Comment
RE: Shouldn't this say "suck less on IIS"?
by google_ninja on Thu 30th Jul 2009 19:06 UTC
in reply to "Shouldn't this say "suck less on IIS"?"
RE[2]: Shouldn't this say "suck less on IIS"?
by Tuishimi on Thu 30th Jul 2009 19:53 UTC
in reply to "RE: Shouldn't this say "suck less on IIS"?"
RE[2]: Shouldn't this say "suck less on IIS"?
by memson on Fri 31st Jul 2009 08:35 UTC
in reply to "RE: Shouldn't this say "suck less on IIS"?"
RTFA, they barely talked about IIS, more about the build process for windows, and the external libraries used.
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.)
RE[3]: Shouldn't this say "suck less on IIS"?
by google_ninja on Fri 31st Jul 2009 11:56 UTC
in reply to "RE[2]: Shouldn't this say "suck less on IIS"?"
RE[4]: Shouldn't this say "suck less on IIS"?
by Johann Chua on Sat 1st Aug 2009 11:57 UTC
in reply to "RE[3]: Shouldn't this say "suck less on IIS"?"
RE[4]: Shouldn't this say "suck less on IIS"?
by segedunum on Sat 1st Aug 2009 23:26 UTC
in reply to "RE[3]: Shouldn't this say "suck less on IIS"?"
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


