I gotta agree with Christopher on this one.. I have zero intentions of
using the 'Registry' in 80%+ of my projects.. I find that the
controllers invoke params suit all my needs. As for debug, I simply
cant find any justification for loading that into production/runtime..
To reiterate a very important point I've made in the past (actually 2):
http://www.nabble.com/Re%3A-Request-for-feedback%3A-moving-Zend.php-to-Zend-Zend.php-p9152637s16154.html
1) this adds to the schizophrenic nature of the class. (what does it
really do?) and,
2) its a bad thing that the first file presented to a new
ZendFrameworker is an 'exception to the rules'
I think we should still set aside performance hacks until later.. which
ultimately seems to be the only reason for doing this.
my 2cents.
-ralph
Christopher Thompson wrote:
The only real reason given for Zend/Core.php containing four classes is
for performance, but I think it will actually have the opposite effect.
The only class really used in the framework is Zend_Loader. Exceptions
are lazy loaded, the Registry is a userland thing, and the
Zend_Framework class is only informational. All that is minimally needed
is Zend_Loader, so with Zend/Core.php you are actually loading a bunch
of possibly unused code every request.
