pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Finner <postgresql@finner.de>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: brion@estaffing.net
Cc: pgsql-php@postgresql.org
Subject: Re: Interview questions?
Date: Sat, 20 Sep 2003 22:42:07 +0200
Message-ID: <20030920224207.10f1353a.postgresql@finner.de> (raw)
In-Reply-To: <3F6C8F81.6090509@commandprompt.com>
References: <000a01c37d8e$d8dc2540$026fa8c0@global.cadence.com>
	<20030919230841.6a4ad00f.frank@finner.de>
	<3F6C8F81.6090509@commandprompt.com>

On Sat, 20 Sep 2003 10:33:53 -0700 "Joshua D. Drake"
<jd@commandprompt.com> sat down, thought long and then wrote:

> 
> >I used to be a PHP-user for a long time, but these problems with
> >different PHP versions have brought me back to the usage of Perl CGIs
> >with FastCGI. Never had any problems with that combination yet,
> >excellent speed, excellent stability, no release version related
> >problems. YMMV.
> >  
> >
> 
> You can run into the same problem with perl. It is just a matter of 
> knowing what you are doing (this is not a slam).
> It is my experience that there are a lot of would be programmers who 
> claim PHP experience that really don't
> know what they are doing. Perl at least, to some degree can be 
> intimidating and will scare alot of those same people away.
> 

I agree, and I think this holds true for most programming languages for
which there is no real well defined standard (as is for C for example,
but again not for it´s additional libraries), but updates for PHP are
extremely frequent compared for example with Perl. I use Perl 5.6 and
5.8, and I have found absolutely no backward compatibility problem (at
least not yet :-) ), and I use PHP 4.0.6 and 4.3.3, and have to
fix lots of backward compatibility problems there, sometimes perhaps
simply caused by unclean (but in earlier PHP releases
allowed) programming style. Between these releases is a period of two
years, with Perl and PHP, but PHP released a lot more versions during
that time than Perl did. And they still discourage the usage of PHP with
Apache 2 (see http://de.php.net/install.apache2), which is for me also a
major drawback to use PHP.

But regardless, what programming language and environment you use: The
main point is: If you have problems with an application on different
environment, take everything into account as a reason: Database,
programming language, external modules, webserver, even different
browser releases can cause strange problems (for example, if you use
Javascript for input checking). Usually problems are caused by more than
one reason at the same time...

Have a nice weekend,

Frank.



view thread (8+ messages)  latest in thread

Message-ID: <20030920224207.10f1353a.postgresql@finner.de>
Permalink:  ../20030920224207.10f1353a.postgresql@finner.de/
Also on:    postgresql.org/message-id/20030920224207.10f1353a.postgresql@finner.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: postgresql@finner.de, jd@commandprompt.com, brion@estaffing.net
  Subject: Re: Interview questions?
  In-Reply-To: <20030920224207.10f1353a.postgresql@finner.de>
  References: <000a01c37d8e$d8dc2540$026fa8c0@global.cadence.com> <20030919230841.6a4ad00f.frank@finner.de> <3F6C8F81.6090509@commandprompt.com> <20030920224207.10f1353a.postgresql@finner.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox