On 3 January 2012 15:21, Ben Coman <[email protected]> wrote: > > I am reminded of an article "Things You Should Never Do" [1] by one of my > favourite authors. This is not to discourage the clean out and > re-architecture of Pharo which is overall a good thing, but just to consider > the downside and risk as a counter-point. Certainly Pharo is more evolving > than starting from scratch... > And then I got sucked into reading another (perhaps offtopic) article > "Painless Functional Specifications" [2] that some may find interesting > > [1] http://www.joelonsoftware.com/articles/fog0000000069.html > [2] http://www.joelonsoftware.com/articles/fog0000000036.html > >
yes, a new is not necessary better than old. And if you ask me, i never throw away stuff, just because it is 'old'. if its in good condition and still can be used, why we should throw it away? To my experience, all code we thrown away in Pharo (where i participated) were because it is no longer used or was replaced with better , cleaner, simpler , more robust implementation. -- Best regards, Igor Stasenko.
