Re: Why PHP ? part 2

One more followup: I've not seen any good templating methods in ASP. IIS5/ASP3 might resolve that, and the server.excute method would probably allow for more templating flexibility, but nothing like Perl or PHP templating systems exist, to my knowledge. Yes, someone will say 'I saw X on site Y', but there's not an industry-supported templating standard in use on NT sites. The MS 'webclass' thing is interesting, but too slow for production machines needing speed. Also, my own observations were backed up by an MCSE at a local MS shop - ASP is more and more being used as the glue for COM objects, for performance reasons. So you not only need to know enough VB to put together the framework, you then need VB or VC knowledge to compile your code into fast libraries. This *may* not be as necessary under IIS5, but many places are already moving in that direction, and have money invested in that method, so it may continue even if it's not necessary performance-wise. Yes, it's all anecdotal, but... the only 'official' stats you'll get are from MS marketing anyway. Unless you can find some MS shops willing to be honest and frank with you. I don't think you'll find too many - not at the high level. No exec that's just pushed their company into a strategic direction towards MS, thereby committing untold $ (millions?) towards MS methods, is going to say 'I made a mistake'. They'll bite the bullet and make the IT people jump through hoops to get it work, come hell or high water. And I've seen people on the non-MS side do the same thing. When an MS product made sense economically, people still wouldn't use it, preferring instead to roll their own. Long term, that may still be the best decision, but it's often hard to separate long-term thinking from short-term knee-jerk reactions. Even if it's not knee-jerk, some people will think it is. Good luck! Jeff Demel wrote: > We all now that, huh? > > Again, WHY does it suck? What's wrong with VBScript? It is VBScript, not > Visual Basic that ASP uses, but remember you can also use PerlScript, > JScript or any other language you want (as long as there's a scripting > module for it). You could probably even use PHP, if you had the desire to > write your own module. But what's important here, I think, is providing > specific examples of why one should choose PHP over ASP/VBScript or > whatever. > > So let's get down to nuts and bolts and specific examples. > > -Jeff ========================== Michael Kimsal http://www.tapinternet.com PHP Training courses http://www.tapinternet.com/php 734-480-9961