Ed's recent blog post labeled the The MicroPHP Manifesto got a lot of attention. [...] In general I totally agree with Ed on the point that we need more decoupled components in the PHP world. The timing seems a bit odd since exactly that seems to be an emerging trend with all the various libraries cropping up since PHP 5.3.

He gets into more of his thoughts comparing the recently popular microframeworks to the full stack, broad use case frameworks that try to provide everything you might need. He talks about the difference between them related to configuration over code and when he sees is a good shifting point to move from the simpler micro world to the full stack (hint: business logic).

So the key take a way point is that when choosing to go micro or full stack its very important to consider in what kind of company on what kind of products you are working on.

TechCrunch is announcing Google's new "App Engine" service being launched this evening. The basic service is a full app stack hosted and managed by Google, providing a web framework (maybe I'm misreading this?) and the Google 'big table' database service. [...] My question is "why was Python was chosen instead of PHP?"

There's been some great responses since it was originally posted including everything from agreement to rationalizations for the move (though there is a fair amount of PHP and Python bashing going on - an obvious occurance).

Today's special guest is Chris Hartjes. Chris has been building PHP applications since 1998. Currently employed as a Senior Developer for the Cake Development Corporation, Chris has been labeled as an "agent provocateur" within the PHP community. [...] Today Chris is going to talk to us today about Glue Frameworks vs. Full Stack frameworks.

The show can be downloaded directly from here or, as always, you can drop the url to their feed into your favorite aggregator and get this and other great episodes of PHP Abstract.