Re: PHP Vs ASP
| From: | Chris Adams | Date: | Sat, 29 Jul 2000 00:54:40 +0000 |
| Subject: | Re: PHP Vs ASP | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-8900@lists.php.net to get a copy of this message | ||
> Depends on how well you know to look Chris.
You're correct only if by "how well you know to look" you mean "how to
magically tell which parts of the Microsoft documentation are completely
wrong and which are correct".
I'm not talking about things being undocumented. I'm talking about specific
documentation which is wrong, where the sample code is also wrong and has
very basic syntax errors which imply it at no point did anyone even attempt
to run it, let alone debug it. Fortunately, there are sites like
DejaNews.com which can be used to find out how something really works.
> Having said that, I guess I believe in using BOTH asp and php, they have
> their own advantages. When you are talking about sophisticated
> enterprise-level apps, sometimes components are the MOST sensible way to
go
> if you care about code-maintainability and reuse.
This is completely unrelated to anything I wrote, and is a completely
separate issue. You can write modular code in PHP, ASP or any othe
language/environment in existence. The difference is that ASP limits your
choice to COM, which must be used to do anything beyond very basic work
("<%=1+1%>"), requires the use of multiple languages and environments and is
slow and hard to debug.
> I dislike Java because of the rigmarole attached with coding/debugging etc
It's no worse than any other programming environment in that regard. It does
have the advantage of avoiding many of the debugging issues you'd face with
something equivalent like C++ and it's nice to have something portable.
> and PHP doesnt support any component based development yet, of course we
There's support for COM, Java, extensions, and object orientation.