Chris Shiflett <[EMAIL PROTECTED]> wrote:
>--- James G Smith <[EMAIL PROTECTED]> wrote:
>> PHPUnit is available, first release was April, 2002. First
>> production release was mid-March, 2004.
>
>I didn't say this stuff was old or mature, just that it exists. :-) Truly,
>PHP feels like it is just
[EMAIL PROTECTED] wrote:
> I'm not sure I understand how XHTML can replace TT, H::T, or Mason.
> Could you provide an example? My understanding is that XHTML is just
> an XML-ized version of HTML, so it retains all the form controls from
> HTML; an tag in HTML is just an element in XHTML.
>
He
Hi,
This is a very good example of why it is pointless to get into, Perl can do this and
PHP can't.
The fact is, much of that is crap if you dig enough. Just like saying C can do
something Perl can't, big deal, Perl can use the C code and move on.
The reason I avoid PHP in particular for big a
--- James G Smith <[EMAIL PROTECTED]> wrote:
> PHPUnit is available, first release was April, 2002. First
> production release was mid-March, 2004.
I didn't say this stuff was old or mature, just that it exists. :-) Truly,
PHP feels like it is just now reaching the maturity level that Perl
enjoye
Rafael Caceres <[EMAIL PROTECTED]> wrote:
>On Wed, 2004-06-09 at 13:58, James G Smith wrote:
>> Chris Shiflett <[EMAIL PROTECTED]> wrote:
>> >Not to discourage any PHP bashing (I'll often join in), but a few things
>> >on your list aren't really that accurate:
>> >
>> >--- James G Smith <[EMAIL PRO
On Wed, 2004-06-09 at 13:58, James G Smith wrote:
> Chris Shiflett <[EMAIL PROTECTED]> wrote:
> >Not to discourage any PHP bashing (I'll often join in), but a few things
> >on your list aren't really that accurate:
> >
> >--- James G Smith <[EMAIL PROTECTED]> wrote:
> >> o No support for testing
Chris Shiflett <[EMAIL PROTECTED]> wrote:
>Not to discourage any PHP bashing (I'll often join in), but a few things
>on your list aren't really that accurate:
>
>--- James G Smith <[EMAIL PROTECTED]> wrote:
>> o No support for testing
>> o No support for documentation
>> o No way to declare v
Not to discourage any PHP bashing (I'll often join in), but a few things
on your list aren't really that accurate:
--- James G Smith <[EMAIL PROTECTED]> wrote:
> o No support for testing
> o No support for documentation
> o No way to declare variables / manage typos
PHP has these particular
[EMAIL PROTECTED] wrote:
>James G Smith <[EMAIL PROTECTED]> wrote:
>>
>> For many applications, you are correct. However, some situations
>> require support of the most basic systems.
>>
>> Part of the problem with XHTML is that it is a page description
>> language instead of a se
James G Smith <[EMAIL PROTECTED]> wrote:
>
> For many applications, you are correct. However, some situations
> require support of the most basic systems.
>
> Part of the problem with XHTML is that it is a page description
> language instead of a semantic markup language. We need
[EMAIL PROTECTED] wrote:
>This is also what I am trying to suggest. Back to your other post
>yesterday, I may propose that you go directly to the XHTML and use
>libXML to parse data into it. The modern browsers (the latest IE and
>Mozilla) themselves understant XSLT tranlation and so even this pa
James G Smith <[EMAIL PROTECTED]> wrote:
...
>
> The conclusion seems to be that PHP is nice for small systems and
> applications, but for larger, more complex projects, mod_perl is the
> only one of the two that can compete with the expectations coming
> from the Java side (which, as much as w
While we're talking about mod_perl, perhaps I can throw out a few
reasons why I have chosen it over other languages and technologies.
This might help us figure out where we need to do some intial PR
work.
We currently have our account management code using PHP (this is for
about 100k accounts). W
13 matches
Mail list logo
