memory model, its runtime and historically conditioned limitations #11
Description
when a new entity is created for a mixin, the first use is certainly in the main routine that triggers a test. but at the latest before the release date, it must be determined under which circumstances the entity undergoes a mixin: constantly pre-built in the release blob? usable for an update (rebuild) procedure? latently available as soon as an HTTP request requires the properties of the new entity? these and other considerations lead to requirements for the memory model that are not met by Squeak, for example; to prove this, try redefine the Set class with a new instance variable. do you see directions in the development of the Newspeak runtime that can eliminate historically conditioned limitations? I'm looking for, change anything anytime "hindrance" …
P.S. small typo psuedo in stellar design.md ;-)