Most of Rasmus' compaints are about performance. Performance is a key factor if you are creating a language like PHP, but performance is not that important if are creating a web site, or application. If you take Rails as an example, it was really slow, and people adopted it anyway because it made things easier. If your application gets popular and you need to optimize it's performance you have plenty of options, from caching to writing pure PHP. Using Zend Framework as an exemple, it's not it's performance that annoys me. What annoys me is how long class names are, how complex things are not made simpler, like Rails did. When ZF came out it took me hours just to start a project, and even now i need to open the documentation every time i need to use a component, cuz names are so long, and i personnaly don't like how things work. I was PHP developer 5 years before the first time i used Rails, and i'm not happy to say i know (and like) more about rails now, with 1 project i made using this framework, than i know (and like) about ZF in 3 years using the framework.
Manuel Lemos - 2014-02-05 22:40:01 - In reply to message 1 from Carlos Rodrigues
Not optimizing for performance, means the Web hosting will cost more for you.
The Ruby On Rails case is a perfect example of that. Many sites needed to move away from it because of performance hits. Twitter for instance moved to Java because the Rails solution did not perform well. Rails solution was so bad that they did not have any options to optimize it.
As for Zend Framework, I decided to not comment about it because it was something that Rasmus did not get too specific about it.
But it seems there are many annoyances with it. For instance, the forms classes seems to be so complicated, that there is people creating code generator to call Zend forms classes.