Re: memory usage issues in PEAR 1.4.0

On 3/6/05 11:03 AM Pacific Time, Justin Patrin (papercrane@gmail.com) wrote: > 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. Well said, Justin! It's worth noting that PEAR 1.4 is in an alpha state, indicating that Greg is no doubt fully aware that it's not quite ready for prime-time. Now is when the tweaking and optimization work can _begin_ ... I'm finding the tone of the criticisms in this thread more than a little hard to believe. -Clay -- Killersoft.com