Re: [MacPerl] Competitors

[Arved Sandstrom <Arved_37@chebucto.ns.ca>]

I think (I can't say for sure) that PHP is fairly scripting-language 
agnostic. That is, the tags themselves are PHP but the scripting language 
can be Perl or a number of others. Like I say, I can't swear to this.

Never heard of Aestiva so can't comment on that one. :-)

ColdFusion and Perl just don't cooperate in that sense. CF already has so 
much functionality for DB access or doing most anything else that you 
basically use it, and don't really need anything else. If it did need to be 
extended you'd use C++ or Delphi for custom tags, or call out to Java 
classes or CORBA objects, etc etc. Painting a very broad picture, that is.

I'm a big fan of Perl, and always have been, but if a client came to me and 
said that they were willing to accept the risks of investing in Allaire's 
proprietary approach (ColdFusion, IOW), I'd find it difficult to muster 
plausible arguments to dissuade them. As a matter of fact, from a client's 
point of view CF is more attractive precisely for the reason that the code 
is much more accessible to them - Perl has a substantially greater learning 
curve. :-)

You'd need to check up on it, but of the client isn't amenable to pure Perl 
but you'd like to keep Perl in the picture, then maybe PHP is the approach 
to push.

OTOH, from a pure business standpoint maybe the capability of doing some 
mods themselves is fairly important to the client. In which case you can't 
discount that, and need to ensure that as unpleasant as the alternative 
development environment is, the client is happy with it. And you make sure 
the client _owns_ the project by the time they start making mods to it. :-)

Arved Sandstrom

At 11:24 PM 5/30/00 -0400, Mike Pasini wrote:
>I'm holding a Perl tail in my hand and a client is spinning me around with
>PHP, Aestive and ColdFusion for a small relational donkey ... er, database
>... which I'd like to pin the tail on.
>
>It seems to me PHP, Aestiva and ColdFusion exist for people who don't know
>Perl (and, in this case, SQL). Otherwise I really don't know how they might
>complement Perl.
>
>In fact, the client is attracted to the idea they might make minor mods to
>the entry/reporting system themselves if they invest in Aestiva or CF.
>Which scares me.
>
>Can anyone here point me to a resource (other than the product dot coms
>I've already visited) or make an argument for or against any of these
>approaches? Am I even asking in the right place?
>
>In return I won't dare ask how to test this in MacPerl <g>. TIA
>
>:::::::::::::::::::::::::::::::
>Mike Pasini
>mike.pasini@uwreport.com
>
># ===== Want to unsubscribe from this list?
># ===== Send mail with body "unsubscribe" to macperl-request@macperl.org
>
>


# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org