I remember reading about some issues with sharing traits code, however I don't remember exactly the problem. But it seemed that it can be fixed... Can somebody refresh my memory on that?
If it is only an implementation problem maybe we can fix it... In that case the n*m issue is gone. About using 'self' in nb calls I don't see any problem, it just means that your class uses the trait, and it is doing ffi... On Nov 29, 2012 7:00 AM, "Yanni Chiu" <[email protected]> wrote: > On 28/11/12 9:32 PM, Camillo Bruni wrote: > >> >> where? memory is the only thing you may waste, and we still have plenty >> of it >> to waste. >> > > That's the kind of thinking that can lead to things like needing 100's of > MB of RAM just to run the Java-based install programs. IMHO, conserving > resources is always important, and some times has to be traded-off. > > 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... >> > > You said "hardly ever care", but when you care - it matters. I'd like to > be able to run many images on a single server. If you make each base image > big, then I can run fewer such images. If it's in the base image, and it's > not striped out by #prepareForProduction, then it's a problem. > > > >
