Comment by smupp

And what happens to the VM when the user closes their arc app? It seems like you could build really powerful tools that leverage saving the state of the VM between sessions. Suppose I build an arc text editor/image manipulator, something where my workflow is boot program --> load file X --> edit file X --> save file X. In theory I could save states of the entire app between sessions, so the whole workflow becomes boot arc app --> edit file... And I could do this for any app I build in arc... Am I getting this right? Because that would be absolutely incredible for building session persistence without a home-brew backend.