zlacker

>>speckx+(OP)
To get Perl to work with apache (the most used web server for a time), there were two options: the not-so-complicated cgi script which gets executed from scratch on every request, then there was mod_perl which required a lot of tinkering with apache configurations and writing your code in a different way.

Even with those two options, you can't just write some code in a page and execute it without some sort of itermediate code.

Thats why php became so popular, perl coders could pick it up in a day ($ and all) and all you have to do is write .php files to a server - with the bonus that you have a rudimentary templating system built-in to php.

There really isn't much more to it than that.

>>dana32+6v1
This is why I preferred Mike Migurski’s nickname for PHP: Apachescript; easy to integrate to the web server and next fastest thing to C for Apache.

>>riorda+Ev1
I had to do a double take when I learned that modern cloud services still support PHP.

Mentally, I put it in the same bucket as legacy ASP, which is looooong dead.