Re: [Fwd: Re: [PEAR-DEV] MVC revisted]

Well the problem is that PEAR is not really a framework. The only true framework components of PEAR are PEAR (class) and PEAR_Error. While, in some ways necessary to work around deficiencies in PHP4's object and error handling model, they represent the most detestable parts of PEAR and the parts that cripple PEAR in PHP5. Think about the attempts to write PEAR class as an extension to speed up the code. Think about why Cache_Lite tries to do lazy initialization of PEAR_Error. Framework code can get very dangerous. Especially in a short-lived code like a PHP web script. Isn't it bad enough that we are restarting the PHP engine, retokenizing all the scripts, unserializing our session and session objects every cycle? Do we really need to add restarting framework objects? Also consider that while PEAR doesn't have very much framework, very many frameworks use PEAR. Many of you know that I'm big on O-O. But lets temper that with a bit of practicality. Take care, terry chay