Why are you talking about character-phobia? Collections.sort(list);
contains at least one more concept compared to: list.sort(); If you think the only gain here is saving some characters, we should just stop right here and agree to having a fundamentally incompatible logic concerning language development. Your entirely dynamic solution concept is available now in java, just stick that 'lookup' method on something. However, to make the boilerplate go away, you'd need mixins/traits. I take it you're a fan of those, then? Something we can agree on, at least. On Nov 22, 4:44 pm, Fabrizio Giudici <[email protected]> wrote: > Fabrizio Giudici wrote: > > A design which implies that behaviour is *static* rather *dynamic* is > > a worse design (especially if this is the consequence of a phobia for > > a few characters more), and this is an objective consideration from > > OOP best practices, not a subjective one. > > Just to have a better real-world example which is not List, I've at last > managed in finishing another blog post that I had in draft since some > time, and explains what I mean: > > http://weblogs.java.net/blog/fabriziogiudici/archive/2009/11/22/when-... > > So, just to keep the focus on our discussion, would it be possible to > make the same things with extenders? > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > weblogs.java.net/blog/fabriziogiudici -www.tidalwave.it/people > [email protected] -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=.
