> Let's compare it with the jre, or with tomcat or so. They are stuffed > with classes I can do without, and I'm glad that I don't have to install > an aditional package for every feature I could also have done without > before that point. The jre and tomcat both define services. and when a choice can be made(xml,pooling,jsp compiler,web version) they provide interfaces to change the implementation, Yes they do provide a lot of features and just like for mmbase I don't think this is a bad thing. still the core must be a clean/small as possible.
> > It's good that we break up mmbase in modular pieces, but we should not > exaggerate, and that we should not use the mere argument that we can 'do > without' a certain class, because then I fear there will be no end to > it.... I think it's up to the release manager to define what will be standard in the next release. jai or image magic, for email and database stuff we don't have that luxery because it's all stuffed in the core. _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
