That 'quickly' part is not a prerequisite for a full-stack definition
I wasn't sure whether he meant 'quickly' as in performance while running or 'quickly' as a complement to the time it takes to get up and running. I think you are assuming the former? In which case I agree and disagree, what else is new?
I think performance is important, no question about it. If framework A runs 5 times faster than framework B, that is (in theory) 5 more web sites I can host on a rented server before having to shell out more money for a new server. Maybe an extra 50-100 bucks a month.
Time is money.
That being said, while Zend is slower (and Magento has done nothing to demonstrate the speed or ease of using Zend, it does demonstrate that it's capable of building large scale applications, but it's still a horrible textbook example, if that is what it's supposed to be) computer performance is always less important than developer performance, which is widely accepted -- I think you'd have to be a fool to disagree with that logic.
So if Zend fits your coding style, you don't mind getting dirty with "more" details than say CodeIgnitor, the winner is clear.
In an enterprise (or business other than my own) Zend is a clear winner. It's documented as well as most (CI is just easer to comprehend as it's default setup lets a developer start implementing actions instantly -- no bootstrap setup, etc -- which is exactly why I dislike it), it's performance is not so bad it's unusable -- otherwise no one would use it -- and it is very flexible in design -- far more than CI hands down.
Did you read my post? I said that Zend's is harder to get into than other frameworks, and therefor would take more time to set up. That doesn't mean it's not a full-stack framework. There's no relationship between the learning curve and how "fully stacked" a framework is.
With my understanding of "full-stack" I would tend to agree that Zend is very much full-stack. When I asked that question, I was actually interested in arborint's exact definition, just to see if it differed from my own, but I appreciate your feedback anyways markusn00b.
Full stack is a framework that provides all nessecary components to get any enterprise software implemented. You can build both CLI and Web based apps and would not likely have to go outside the Zend framework for anything additional -- whereas my own in house/personal framework depends on third party libraries such as Swift, DataMappers, OpenID lib, etc. It is far more minimalistic than Zend.
Although I do know what you mean by glue framework as well. Not a fan of that term, I would prefer dependency injecting (or similar), to describe what the extra steps are really doing when you use Zend.
CI is ready to go out of the box, Zend assumes you are interested in setting everything up -- which many developers are -- myself included.
Cheers,
Alex