> > An Extreme programming rule: Do The Simplest Thing That > Could Possibly Work. > > The requirement now is to have one handle field and the current > > implementation does work. No idea why it should be over-designed > > You keep saying stuff like that and it might be wright for > projects you do for customers. > but a thing like mmbase must be ready to be extended and even > used i way's you never would have imagined. Things should be > logic not simple
I can't agree on that. A small, simple application that does one thing well is much more valuable than a hundred applications with lofty goals that never actually do anything. There's nothing wrong with writing a framework, provided you really need it. It's much easier to generalize a framework out of working projects than to design a framework to fit future, uncoded projects. These future projects will show where mmbase is not extensible and what has to be changed to fit the need. Something being logical is based on earlier or known statements or conditions. Hard to read source code with too many features will redefine being something logical to being wrong with confidence... The things that are logical now are not always logical in the future. The ways in how mmbase is used will change over time and new ideas will show that things aren't as logical as we thought they would be. How these changes are managed will make mmbase successful or not. I replied on Michiel's suggested "change" to leave it off the todo-list, because it has no return on investment at the moment. I used a very big word (over-designed) to emphasize this. From the time I started using mmbase up to now the handle field seems okay for me and according to the code it is reasonable too. Nico _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
