Re: memory usage issues in PEAR 1.4.0

Yes, spot on there, that bit was a bit badly phrased, I do appreciate all the work, and as Greg says, nobody has stepped up much to help, and all he hear's are complaints, which is not really what the thread is about. I was attempting to motivate (and failing badly) thought about refactoring (slowly, not instantly..) to consider performance and speed.. Regards Alan

Alan: You may have wanted to phrase things a little better. To intimate that perhaps we should "throw out the bathwater" on the work he's done for more than the past year *ALONE* is simply not appropriate. I can understand Greg's anger when you say that the features he's been sweating blood over should just be pruned. Where was all of this back when Greg was working on the project? There was virtually no discussion about much of the new features and the code while Greg was working on it. Dont get me wrong, you do have a point, Alan, but coming in at the end of the pipe, when things are nearly ready to be released, and offering some thoughts without any real work is destructive. First you complete the code (and make it work correctly) and then you optimize. It you want it optimized, I suggest you dig into the code and figure out where it can be optimized. Don't just suggest cuttong features, figure out if things can be lazy loaded, profile the code, find the resource hogs, and find a way to reduce their memory consumption. Greg has worked on all this for quite a bit of time he put things where they are for a reason. If you want to help, pony up. Don't just say that we should trim things.