4 ms·
> I abused the Resource Manager and a file's resource fork to serve as a crude VM Abused? That’s what it was designed to be. https://www.folklore.org/The_Grand
by Someone 2y ago
> I abused the Resource Manager and a file's resource fork to serve as a crude VM
Abused? That’s what it was designed to be. https://www.folklore.org/The_Grand_Unified_Model.html https://www.folklore.org/The_Grand_Unified_Model.html:
“Thankfully, I knew of a similar system in Smalltalk, an object-oriented virtual memory called OOZE that was designed by Ted Kaehler, that swapped objects in and out of main memory as required. This was my inspiration for the Resource Manager. Find out more about OOZE here”
- tmoertel 2y agoI think the Resource Manager was designed with the "objects" in mind being understood to be an application's assets, such as code, graphics, menus, text, and so on. My abuse was to extend this to arbitrary, dynamically allocated blobs so that an app could, for example, scan thousands of files and store each file's metadata in virtual memory, way beyond what would fit in RAM.