Proposal for a new data structure that extremely reduces data sizes for data in which two item types

I went and read the overview, not in its entirety as I'm just kind of checking some notifications and trying to move on to a project. I downloaded the paper to read-at later. Just wanted to say that I had thought similar to 'storage and time' while getting fairly deep into playing with Javascript, specifically in regards to its prototyping (I still have my test scripts around here somewhere) I found that I could, via prototypical inheritance, allow an object to be 'knowledgeable' of and read values from both its 'past' prototypical state to and from its own 'future' states. Future states could reach back to a previous state and read from it. I could write, overwrite, and recall prototype constructors and then recall them from a past state, as well as being able to roll them up and roll them back out again* (I'd figured this out while attempting to convert these objects to valid JSON strings (because, obviously, having so much chained structure disallowed conversion to and from in any normal way). *Can't remember if I was completely successful)

Disclaimer, what looked something like time-like data traversal really might have just been typical proto behavior (have never found a needed to use the behavior in the extent I was playing with then (AngularJS had some issues with the way it handled data flow some while back, did some fairly deep trickery there to patch it for a project but the trickery was only similar in nature the these prior objects, Angular mostly fixed the issue themselves and is not much of a problem any longer).

- I moved on to another project and stored the script. Best to let smarter people handle such things, I'm sure I had no idea what I was doing. 😉  I do always intend to get back to experimenting with the things I play with. Sometimes I do, sometimes I don't.