On Jan 6, 2014, at 11:31 AM, Otto Behrens <[email protected]> wrote:
>> Some core objects (Blocks, CompiledMethods, etc.) could benefit from >> having a developer string representation (#printString) and a UI >> string representation (#displayString). > > I don't really understand why. How would you distinguish between which > (kinds of) core objects and which not? Will you not end up with a > displayString on Object again? You will not know all the 'why's in advance. The concrete answer is in the next developer's creativity. What you can do in advance is to ask 'why not?' And a reason that comes to mind to answer that is: because 1) what are the odds to NOT needing to perceive an object? 2) what's the most obvious way to make objects perceivable one if not displayed as a string in some kind of screen/device/hologram/network-proocol/whatever?
