Re: PHP Vs ASP

> Owen, seems to be into some pretty deep development, very important > stuff I presume. Discover a major bug with ASP and discover one of same > seriousness (<-- I don't think that's a word) with PHP. Owen, how long do > you see yourself waiting with ASP and how long do you see yourself waiting > with PHP? With ASP your life, livelyhood and everything else is in someone > elses hands whereas PHP you're only limited by how 'dirty' you are willing > to get your hands. Roll up those slevees and fix it yourself if worst comes > to worst. Try doing that with ASP without going to jail. That's one of the best advantages to PHP. Awhile back, I discovered a show-stopping bug in one of the PHP4 betas shortly before a site was supposed to launch (for a variety of reasons, we had to use PHP4 on Win32, too. Not my choice.). Zeev sent me a fixed build a little over two *hours* later. In contrast, I discovered two bugs in Cold Fusion last week (That project's regularly reminding me of why I prefer PHP). One of them has been broken for quite some time; I can't report it directly without paying money (support@allaire.com is routed to /dev/null as far as I can tell) and the only responses I've gotten from a post in their web-based support area are from other developers stating that it's been broken for quite awhile and no fix is in site. The second one is being handwaved (summary: "When it says $OPTION does $FOO, it doesn't mean that $OPTION will actually do $FOO") by Allaire's "support" people. Microsoft is worse. The worst case I've heard about was from a guy who was lucky enough to be working at a site which had an NT source license (some university, IIRC). He sent a detailed report and gave them a *patch* to fix a bug several years ago; the bug has never been fixed. Based on my experiences, PHP's ahead on features, reliability, performance, ease of development, support and price. However, all's not lost for the commercial vendors - they're way ahead on glossy brochures. Chris