pull down to refresh

Unlike traditional code interpreters, ForeverVM does not have a concept of a session after which state expires. Instead, ForeverVM uses memory snapshots to swap idle machines to disk for as long as you want. This improves scalability and resource usage, and means that applications and agents built on ForeverVM don't have to manage session lifecycles.
There’s something so satisfying about this.
swap idle machines to disk
That's how Smalltalk was implemented on the version I had.
All state was saved to disk and reloaded on startup.
It was a little slow (back in the 90's).
reply