David
--- On Wed, 6/25/08, David Rogers <da...@hydrastudio.com> wrote:
> From: David Rogers <da...@hydrastudio.com>
> Subject: Re: Why PHP?
> To: orlan...@googlegroups.com
> Date: Wednesday, June 25, 2008, 10:35 AM
> I was similarly motivated. Having come through CompSci, I
> touched a
> lot of C-type languages: C, C++, Java, etc... My options
> for web
> development were between Perl and PHP, then, since I
> wasn't really
> interested in learning a whole new language for Python
> (there was no
> Ruby). PHP also operated as a simple template language,
> allowing me to
> ease into development rather than jump in head-first.
> I'd imagine that
> the low entry-level barrier for PHP and its similarity to
> other C-type
> languages are the primary draw for the language.
>
> David
So why didn't you go with JSP (Java Server Pages)? I'm just
curious because you mentioned you had a Java/C/C++ background.
--- On Wed, 6/25/08, David Rogers <da...@hydrastudio.com> wrote:
> From: David Rogers <da...@hydrastudio.com>
> Subject: Re: Why PHP?
> To: orlan...@googlegroups.com
> Date: Wednesday, June 25, 2008, 10:35 AM
> I was similarly motivated. Having come through CompSci, I
> touched a
> lot of C-type languages: C, C++, Java, etc... My options
> for web
> development were between Perl and PHP, then, since I
> wasn't really
> interested in learning a whole new language for Python
> (there was no
> Ruby). PHP also operated as a simple template language,
> allowing me to
> ease into development rather than jump in head-first.
> I'd imagine that
> the low entry-level barrier for PHP and its similarity to
> other C-type
> languages are the primary draw for the language.
>
> David
So why didn't you go with JSP (Java Server Pages)? I'm just
I looked at JSP, J2EE, EJB, Swing, Struts, etc... The list continues
ad nauseam. That was really the determinant factor in my exploration
into Java technology. Java seems to introduce too many layers into the
mix, and I wasn't really interested in learning how to setup and run
Unix, Apache, anySQL, Tomcat, a web application container, the
application framework, the ODBC layer, etc for any server onto which I
wanted to develop. That's a whole mess of requirements to juggle for
any development project, plus the expense of even running a server
that met those requirements.
When I started with real web development, I initially just wanted
something that was: 1 - more powerful than SSI's, 2 - as ubiquitous as
SSI was, and 3 - as easy to use as SSI directives. PHP seemed to fit
that quite naturally and ran on practically every server on the
internet without a lot of configuration. I quickly discovered,
however, that the multitude of configuration options available to me
via PHP and Apache permitted me to do a lot more than simple CGIs and
SSIs.
So, in short, PHP was C-like and worked seemingly everywhere with
little configuration, while Java was C-like and ran practically
nowhere by default and slightly more than nowhere with a lot of
configuration. I still like a lot of the concepts from Java, read Java
references, and can talk shop with most professionals. Patterns are
patterns are patterns, after all, and the language of implementation
is irrelevant.
David
Derek Gallo
Orlando, FL
http://derekgallo.com