- November 29th, 2009
- Write comment
So far, I’m fairly unimpressed by the way it’s implemented. I mean, it’s fine that it’s a work in progress but I’d almost prefer not to have method stubs that throw “not implemented” exceptions in a “production” distribution. Why would you want to frustrate developers with unimplemented method stubs? There definitely needs to be a change in policy for their releases, that’s all I’m saying.
Also, what is up with this spotty reference manual and completely unintuitive API documentation? Zend Framework API reference PHP documentation is about 10 years ahead of this disaster. It took me about 30 seconds of staring at the front page trying to figure out how to change packages. Also, I love how the reference manual has areas where they reference things that haven’t been implemented yet. I don’t mean reference as in a sentence, but in the actual coding example. In fact, that was the first time I ran into the “unimplemented” exception.
Thanks for the underwhelming experience, Zend. I think it’s a noble pursuit, but poor documentation really hurts the experience and usability.