PHP Programming (was JOB: LAMP Artisan)

Joshua Marsh joshua at
Thu Mar 6 17:41:40 MST 2014

On Thu, Mar 6, 2014 at 4:40 PM, Levi Pearson <levipearson at> wrote:

> Anyway, it's a difficult problem, but we don't do anyone any favors by
> shrugging and accepting the status quo, or by failing to really
> analyze the problems we have and how they should really be solved,
> rather than just accepting that "what everyone is doing" is really the
> way things should be done.
I don't think I'm shrugging it off. I just think that zealots and academics
don't typically represent reality. The blog post was clearly inflammatory
and he didn't iterate anything that wasn't already known to me or the
public in general. Everyone has an opinion. He clearly has one about PHP.
Regardless, people still use it and new projects are using it.

Don't get me wrong, I see your point about moving forward. I'm constantly
suggesting new tools and languages for projects. New and sparkly is fun for
academics and my basement. It may even work out well in the startup market.
The problem is that we haven't figured out what all the risks are of using
these new technologies. PHP has been around long enough that the risks and
remedies are fairly well defined, some of the remedies have even been
automated. That risk analysis tends to be more important (at the company I
work for, substantially more important) than language design or the poor
standardization of function names.

More information about the PLUG mailing list