The move seems to enforce memory-always, not file-based dyn linking. Whatever is sitting in the memory that responds to the established API. On the first look

The move seems to enforce memory-always, not file-based dyn linking. Whatever is sitting in the memory that responds to the established API. On the first look it's not that different from how this works now. However, I'm thinking of the next step where the 'system cache' is not even local to the PC, like in a case of a netboot the whole or core set would get downloaded from the remote server be it Apple's or your friendly custom provider/employer. MacBook Pro VT. It's a stretch, of course...