Done. Now I provide my requested suggestion here since theres more room and more feedback.��

Code at the level of individual methods should be source-content-addressable, by a hash similar to but not necessarily identical to git internals (https://git-scm.com/book/en/v1/Git-Internals-Git-Objects).�� Then code can be simultaneously stored to multiple locations - memory and/or separate writable local file as a cache, plus a remote content-addressable database and/or POSTing to a simple HTTP server. �� Code lookup can equally search multiple locations, update a LRU cache and easily purge it if memory is constrained, since the identity of the method source remains the *same* in all cases.

Further, I envisage an IoT future with Pharo running bare-metal on embedded microcontrollers** that don't even have a file system, but do have ample internet bandwidth.�� When you connect your remote-system-browser to it from your desktop, the microcontroller doesn't even need to look up the source code - it just passes the method's source-content-hash to the desktop and the desktop looks up and displays the source code.�� Code compilation for the microcontroller might be done on the desktop and dynamically downloaded and installed per method��in the microcontroller - just bytecode and source-content-hash!�� The microcontroller never sees the source, and the space saving from removing the compiler facilitates smaller targets.��

cheers -ben

**P.S. The latest cool-kid on the block is the Expressif ESP32

We should cater for such possibilities! Invent the future!