The MicroPHP Manifesto

Great to hear a more thorough explanation of the Manifesto. I still don't agree with it, but I totally see Ed's point.

Informative and entertaining. His ideas were explained well and included many background anecdotes to help the audience come around to his point of view if they were not already there.

Ed did a great job of engaging the audience (Except for Chris who was doing email). As always, Ed presented his thoughts in a somewhat contraversial and thought provoking manner which helped people to understand where he was coming from. It was challenging to answer questions which he felt clearly reflected a personal bias, but Ed was always clear to specify that when it was relevant. He did a much better job than me of not snickering when somebody asked how they could help expand his microphp framework :)

Ed's an entertaining speaker with a funny, casual style. He recapped his manifesto and then fleshed out some of the ideas behind it. The minimalist slides kept with the overall theme of simplicity. I thought his strongest argument came at the end (the future of server-side PHP will be as the glue between client-side apps and backend data stores, so full stack frameworks will be less relevant).

Great job handling a controversial topic, and keeping it fun.

Great start to the conference for me—on a philosophical note. I wish people were less defensive of frameworks and more understanding of the message Ed seems to be bringing across. Great thoughts, and a brave stance to take in this over-engineered bloated framework landscape.

This was excellent - Ed was super insightful & has clearly thought about how to approach his concerns in a constructive way. I love that his voice is out there in the community, this is a thought-provoking conversation that I'm excited see play out.

You don't have to agree with Ed, but you can clearly see his logic laid out in front of you. Mo code mo problems

A great talk going deeper into the (short) Manifesto. Good responses to questions too.

Interesting, and nice to hear someone else unhappy with framework bloat.

Entertaining exposition on Ed's manifesto, lots of valid and pragmatic arguments, and excellent presentation as always!

Loved the brutally honest approach by Ed here - really engaging and entertaining. Refreshing to hear advocacy for the micro-PHP side of things as opposed to "what you can accomplish with large framework X".

I liked that Ed's talk wasn't centered around one "right" way to do things. The main concept I got from this was that you should be able to understand and justify everything you use in an application.

Felt a little bit like preaching the the choir, but I enjoyed the talk and got a few useful talking points out of it

I enjoyed this talk; it was something of a meditation on how the responsibilities of introducing new code into your ecosystem and a reminder that not everything needs to be done with a framework.

Interesting and entertaining talk.

I'm glad to hear I'm not the only one who is fed up with all the monster frameworks out there. Also, if you close your eyes and listen to Ed, you will see Jamie Hyneman from the Mythbusters.

Anyone who listens to the /dev/hell podcast has surely heard the points covered in the Micro PHP Manifesto. It's definitely great to have some alternate viewpoints on how code should be structured and used. Ed has some great points that will appeal to a certain percentage of Developers who may not feel that full stack frameworks are the best way to solve their use cases. He also acknowledges that there are many Developers who prefer the structure that the full stack offers, "and that's ok".

It is great to hear Ed speak on any topic. I feel like he could read from a phone book and it would still be entertaining.

( funny Mythbusters comment from the previous poster. Now that I think of it he is right )

I thought that Ed's talk was very thought provoking. He discussed very comfortably with the audience his thoughts on his "MicroPHP Manafesto." What stuck out to me was he awknowledged that there are places for larger frameworks, just that as developers, we have to be responable and accountable for every line of code that we introduce to our project, and projects with large, complex dependancies can make it very difficult to grok it all. I really enjoyed this talk.