On Wed, Jun 14, 2017 at 3:39 AM, Vitor Medina Cruz <vitormcruz@gmail.com> wrote:

Yes, I ��can understand that, but I will have to practice more with Smalltalk to comprehend better.

Keep some notes.�� When you get to the end and you've had a good soaking in Smalltalk, it would be good to read of how your thinking adapted on your journey from Java to Pharo.

It harder to think back to what you once didn't know. ��

cheers -ben

��

Still I think there are some objects used by large bits of the application that would benefit the design if they have it's creation decoupled and somehow organized, but I am convinced that a simple service locator would do the job :)

On Tue, Jun 13, 2017 at 3:29 AM, aryehof <pharodev@aryeh.sent.com> wrote:
Consider that in Java, one can /only /achieve polymorphic behavior across
objects by using /interfaces /or /inheritance/.�� In Smalltalk one can
achieve polymorphic behavior across objects just by *having them understand
the same message*.

The need to have complex schemes for the wiring of objects in Java is a
consequence of this.