On 2012-12-05, at 07:47, Sven Van Caekenberghe <[email protected]> wrote:
> > On 05 Dec 2012, at 11:05, Henrik Sperre Johansen > <[email protected]> wrote: > >> If the same holds true for the % of objects that are methods, you would >> probably remove around 90% depending on usage pattern during that particular >> week. > > Of course, just because there are no users doesn't mean that a method should > be removed. > But there is just too much cruft on Object, SequenceableCollection, String, > Integer, .. that does not belong there. > At least many of these less general methods should be packages as extensions. > > I am also sure that by 'using the image for a week', Camillo also meant > running all tests, as well as building and running tests for major Pharo > clients (@Stephan). yes of course :) my use-case would include something like - install a couple of huge configurations (here we should include all software that is important to us) - open all UI elements - run all tests and then removing the methods should not happen blindly, but reviewed.
