Is there any "more complex" system which is widely used? I am interested if it has a sense to spend time on researching something better than single-inheritance OOP, traits, etc. Because "Worse is Better" is maybe the point.
For example I found easier to improve (optimize) an existing application structure by using traits/aspects/etc. But for a new parts of system it looks easier to think in single-inheritance-objects. About optimisation developers think when it is necessary. Is it? Cheers, Jura El 22-08-2013, a las 16:11, Johan Fabry <jfa...@dcc.uchile.cl> escribió: > > I think that indeed you touch on 2 important cultural issues, first the > entire "Worse is Better" discussion (started by Richard Gabriel), and second > that IDE support is key for getting more advanced forms of modularity in use. > In my experience, sadly, Traits support in Pharo has been less than ideal. In > 2.0 it has improved though, so I am happy about that. > > On Aug 22, 2013, at 4:03 PM, Juraj Kubelka <juraj.kube...@gmail.com> wrote: > >> Interesting. Is it only problem of system complexity? I have the impression >> the problem is that people do not changed his mind in order to think in >> traits. (or generally speaking in any other system like mixins, aspects, >> etc.) It looks like objects with single-inheritance are simple and powerful >> enough. >> >> Or maybe any system like traits have not come with efficient enough IDE? > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >
smime.p7s
Description: S/MIME cryptographic signature
