> > my main problem with traits that number of compiled methods in system > is going to be n*m, > where n is number of methods in trait and m is number of root-classes > where it used.
so? if that is your concern, then you chose the wrong progamming language... > and i am not really happy with that. I prefer having 9 methods in Object than > 9*100 methods in many classes. that's just because traits are a "hack" and copy down methods to make it work, but you as user won't care. > while it is fine from developer's POV (because tools can hide this), > you still paying the price. where? memory is the only thing you may waste, and we still have plenty of it to waste. > just to make sure guys, you know about this, maybe it will lower your > obsession with traits :) I think all your doubts are based on wrong ideas. Maybe if you come from C++ or C yes, but we're in Smalltalk? Modularity and maintainability is what you want to go for! size of objects in memory, specially static objects like methods, is a thing you hardly ever care about...
