Hi Marcel,

> -1
> 
> It makes no sense to officially support a "nil" argument in this protocol.

partially it was already supported officially before (some parameters already were named "aWorldOrNil").

Do you think we should instead modify StandardSystemView >> #initialFrame to use #currentWorld instead of "nil" or are there any semantic differences?

Best,
Christoph