In the latest episode of the "Cloud Out Loud" podcast, Elizabeth Naramore interviews Ed Finkler, most recently known for his MicroPHP Manifesto.

Our own Elizabeth Naramore interviews Ed Finkler, author of the MicroPHP Manifesto.

• The MicroPHP Manifesto
• What was the inspiration for it?
• Let's talk about the controversy around it - where do you think that came from?
• What do you think the impact of the Manifesto has made on the community? Do you think it's given cause to people to rethink their own assumptions?

To listen you can either download the episode (mp3 or ogg) or subscribe to their feed via RSS or iTunes.

Following up from his (now infamous) MicroPHP manifesto, Ed Finkler has this new post to his blog answering some of the common questions he's gotten about his beliefs.

My previous post, The MicroPHP Manifesto, resulted in much excitement. In between fits of rage and crying, I found some time to answer folks questions, and also discuss the topic on the /dev/hell podcast with my cohost Chris Hartjes. To summarize and address some of the common questions, I felt I should write a small FAQ.

Questions asked so far include:

• So you think full-stack frameworks suck?
• You need a large framework to enforce best practices!
• You should check out my microframework!
• How do you choose what gets listed in the MicroPHP code collection?
• Why do you hate Rush?

If you have a question you don't see listed, drop him a note and he'll add to the post with more answers.

The PHPClasses.org site has posted the latest episode of their "Lately in PHP" podcast - episode 20: "MicroPHP vs Complicated PHP".

Earlier in January Ed Finkler announced the MicroPHP manifesto. It seems to be a rant about against the practices of developers that make PHP development more complicated than it should be. This is one of the main topics discussed by Manuel Lemos and Ernani Joppert in the episode 20 of the Lately in PHP podcast. They also discuss the final release of PHP 5.4.0 and whether you should upgrade it or not, the repercussion of the PHP Hash Collision Vulnerability, as well the trends of PHP world based on the analysis of the PHP Zeitgeist 2011 initiative.

You can listen to this latest episode either by using the in-page player or by downloading the mp3.

Lukas Smith has a new post to his blog today with his own take on the MicroPHP manifesto that was posted by Ed Finkler recently. Lukas shares his thoughts on when he sees each type of framework (micro/full stack) has its place and how the project or development team can influence this choice.

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.

Anthony Ferrara has posted his own response to the recently posted MicroPHP Manifesto (from Ed Finkler that has caused quite a stir in the PHP community). In the post, Anthony mentions some of the points he both agrees and disagrees with about the manifesto.

I came across a rather interesting post yesterday entitled The MicroPHP Manifesto. The author made clever use of a very interesting analogy (drum players) to try to prove his point that less is more. The article makes a very interesting read, and I would suggest that everyone reads it. Go ahead. I'll wait. With that said, I have to disagree with the article rather vehemently. I think the message is somewhat right, but for all the wrong reasons.

One of his main points is that he believes in the "right tool for the right job" mentality and suggests that, like the manifesto says, small things are good for some jobs. In other places, though, a full-stack framework (or component-based one) is the right fit. He finishes off the post by going through the manifesto points themselves and adding commentary with his thoughts on each.