There are already some good points made above.
I think in general it was a good idea to keep your talk in English if you practiced that way.
The biggest problem was your volume, once you were not directly facing the people you needed very good hearing to get everything you were saying.
The talk was far from as technical as i expected, but if you are talking about over a year of development and research of things you cant get all the details in 50 minutes :)
I had high expectations about this talk, unfortunalty it did not go in-dept to show us some practical problems that the team faced.
Great talk! I was very glad this wasn't another sales talk.
Would like to see a multi-hour workshop to go in-depth!
Great speaker, and able to present the tool without making a sales pitch out of it - just showing what phpStorm can do for us, PHP developers. Learned a few useful tricks attending this talk.
I'm with Bram on this one. The talk was ok, but I would also have liked to hear more on some of the issues you encountered, and how you solved them (or maybe focus on one issue in-depth, because of the time constraints).
Learned several new small tips about PHPStorm. Everything was easy to understand. And thank you for taking in to account that some of us could not see the screen, you solved this nicely by moving backwards while talking.
Very entertaining and interesting talk, as a PHPStorm user. But, as with the webinars: it's such an information overload. Maarten demonstrates so many things it's impossible to keep up or take it all in.
If a keymap of Mac OS X shortcuts would've been provided, it'd been easier to follow along.
Subject I was very interested in, however Dieter sometimes seemed to be a bit out of his comfort zone (insisted on doing his talk in English while he could've done it in Dutch). Dieter could've spoken a bit louder as it was sometimes hard to understand him from the back row.
He clearly knew the subject and had answers for every question.
As a (new) Symfony dev, I would have loved to hear more about possible problems they encountered, how they fixed or approached certain things (bundles, keeping controllers clean, services...).
Good talk. I may be a bit biased about the topic, but Dieter explained all the stuff we encountered in a clearly manner.
as a 'hardcore' vim user i'm still not convinced :)
but: it was very interesting what approach is taken in phpstorm to solve some usability things, and make the life of the developer as easy as possible.
if i would have been searching for a new 'editor' ;) you could have conviced me.