2009/11/1 Lukas Renggli <[email protected]>: >> But if it so stripped to bare-bones, then where the benefits to use >> exactly Announcements? > > I would rather like to hear what this "more wide functionality" is all about? >
i don't know. I just not buying 'use this' because its good. I need to know why its so good :) As far as i can see, it is as good as any other observer pattern implementation. But alone, this pattern is nothing, so we should analyze, how well it fits for use in different scenarios. And so, what if such implementation doesn't play well with all scenarios, would you still insist to use Announcements instead of making own, given that cost of implementation is quite small (10 or even less methods)? > So far you only argued that big is better. I don't buy that. > In contrary. An annoucements implies to use separate (sub)classes for different event kinds. While i can simply use field in the event to identify its kind. Lets say you having 50 event kinds. So what is bigger - single class + 1 field, or 50 classes? Or we not counting classes as a code? So, as you can see, announcements, in some cases could lead to 'bigger' code bloat. And i would like to know, why it is still good to use them, despite the costs of such potential bloat. > This is old, but "Small is the new big" ;-) > > A smaller infrastructure also means: > > - easier to learn > - less code that rots > - less code to maintain > - less code duplication > - less code to test > - loose coupling > - smaller image > yes, good software is one where nothing left to remove, instead nothing left to add. > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
