My question is this: how did PHP get so many libraries, get installed on so many computers, and attract so much developer attention in the first place? [...] To summarize: Lisp is marketing itself poorly. Lisp either needs to get competitive on the ease of use and productivity front, or lose programmers to other languages.

He mentions this post from Brian Carper and this response as two places bringing up good points about Lisp and its community.

That's one of the things that PHP has going for it over Lisp - the community. PHP's community is constantly pushing, reaching out to the developers with simple tutorials and (usually) useful libraries. He makes a call to the Lisp developers out there, though:

The day will come when Lisp won't be cast aside as a quaint relic of bygone days. On that day, Lisp will be seen as equal to the big languages. And it will learn from and share with them as peers.

What is beautiful code? Ask ten people, and you will probably get ten different answers. Ask them what makes a programming language beautiful, and you've got yourself the beginnings of a holy war.

He compares code to art - the language is just a tool, the canvas an editor waiting to be filled with lines of artist-generated works. Because of PHP's wonderful flexibility, it can be molded to fit just about any need a coder might see fit and gives them the power they need to really dig into the code and about the "paint by numbers" sort fo things language like Ruby have to offer.

In raising the question about whether a specific programming language is agile I want to avoid exploring what makes a language agile, or comparing PHP with other languages. The intention here is not to associate PHP to agile as a natural relationship, as much as to try and understand if we can find the ingredients in the PHP world, for creating an agile environment.

He (Marcello Duarte) first defines agile development practices for those not familiar and talks about the tools that PHP has to offer that fit in with that goal. He notes that PHP fits in well with the goals of agile development in being both light and powerful.

PHPSpec implements a domain specific language (DSL) in PHP for specifying the behaviour of functional units such as methods and objects. The purpose of a DSL was to move away from the xUnit style declaration of tests towards a specification language centred on describing behaviour.

He illustrates with a bowling example - described with a sample class (with a itShouldScore0ForGutterGame test) and how to use it to fit his proposal:

My proposal therefore is to re-implement the current programming language DSL as a specification language - i.e. a new (extremely limited and narrow!) language capable of being parsed by PHPSpec into its PHP equivalent. [...] Using a specification DSL, we can simply ignore the existence of classes in PHP (well, the pretense is nice). Instead the DSL would incorporate a syntax for denoting shared behaviours.

I read about the PHP Implementation of LINQ called PHPLinq. Frankly, I was skeptical about it. Finally, I gave it a try. I still remain skeptical...Let me explain why

He includes an example of a query on an array and how it's "less correct" than a more true to form LINQ implementation. Despite reservations though, he still feels that this implementation of LINQ for PHP has some "cool features" in its own right and it worth checking out.

Now, consider the "average" PHP frameworks. They help you handle request data, manage your output, control app flow - essentially, extending PHP's inbuilt functionality. They are, therefore, PHP frameworks on the PHP framework. PHP provides a vast array (pardon the pun) of functionality out of the box. But when you want to do things your way, it gets out of the way, and this is really important when building anything beyond a simple database frontend.

He suggests that PHP is a "half framework" on its own, providing quick an easy methods and functionality to build up applications. He gives an example of Twitter (and really, who isn't picking on them these days) and how it probably could have avoided a lot of the issues it is seeing if it had gone with something a bit more efficient and flexible.

Be sure to check out the comments for some other great opinions from the community.

Phalanger is a new PHP implementation introducing the PHP language into the family of compiled .NET languages. [...] Phalanger compiles PHP scripts into MSIL (Microsoft Intermediate Language) which can be executed by .NET or Mono runtime.

He mentions some of the features of the tool (including interoperability between .NET and PHP and the ability to use current PHP libraries inside the .NET application). More information can be found on the Phlanger website.

I remember when PHP5 first came out having 'discussions' with a number of people who insisted that PHP5 was way better than 4. [...] Basically, intentions were made clearer with things like "public protected private" (PPP),but I have not yet seen any web project get done faster or dare I say even much *better* due to those sorts of things. [...] This isn't specifically saying PPP is necessarily bad, but that PHP could have addressed the issue in a fashion more suitable to dynamic languages. Keep reading for an example.

His comparison is to how Groovy handles properties in a class - everything is private unless declared otherwise. This could be ported (somewhat) over to PHP and would eliminate the need to search&replace all over the code for the right variables.

So, I was asked in IRC today about the proposed short array syntax for PHP. For those that don't know, I mean the same syntax that other languages (javascript, perl, python, ruby) all have. [...] It just feels like a good addition to the language. It is common among web languages and therefore users coming into PHP from other languages may find it more comfortable.

He compares it with other data type creation in PHP (you don't call int() to make an integer, so why call array() to make an array). However, according to a post from the internals mailing list, we might not be seeing this any time soon.

If you use YAML in PHP, then you had until recently the choice between the C based PECL extension syck or the horrible spyc PHP based implementation. With syck it has the issue that it only supports the core standard and not stuff like merge-key, which is a very very useful extension to the core YAML standard.

He also points out another implementation that the Symfony framework has created - one built around regular expressions (slower, but a "more correct" version).