Recently I was working on a project with a friend and I closed Picotron, thinking it would reopen where we left off. It did not.

We searched through all sorts of Picotron folders to try and find a RAM backup but turned up nothing.

I realise that stuff in RAM isn't saved on a real machine and Picotron might be trying to emulate the experience of working with an older machine, but from a usability point of view, it's suboptimal and disappointing when you lose stuff.

I'd like to suggest either:

• Prompt the user to save when the window manager close request is received
  -or-
• Upon opening, return to the same state the VM was left in

Perhaps a toggle in the settings to switch between both?

Save often and use Anywhen to roll back any changes you may regret.

Personally I've gotten in the habit of saving before every time I run.

Sure, I don't feel that Anywhen necessarily addresses the point I was making as it isn't protecting the delta held in RAM. I've updated my post title as I think it was misleading.

Relying on manual saves as the only safeguard against data loss is problematic design (not to knock Picotron's design in any way - I know it's still in development). Save prompts, autosaves and session restore are commonplace now. I think most people have come to expect them as part of their workflow.

Picotron is clearly designed with approachability in mind and it's really nice as a cozy retreat away from enormous codebases, so I think that adding something along the lines of my earlier suggestions could help make it even more user friendly.

Anywhen only keeps track of saved changes, not anything in /RAM

The solution to this is to learn to hit ctrl+s often, and before you run the cart.