This is clever, but running in a VM with hibernation is a lot easier, more consistent and more comprehensive (all state is saved, and restored instantly)
This is clever, but running in a VM with hibernation is a lot easier, more consistent and more comprehensive (all state is saved, and restored instantly)
But the VM needs reboots too, kernel upgrades for example.
And if you upgrade libraries, especially for security issues, you need to restart apps dependent upon them, needrestart in Debian helps greatly with this.
So a VM doesn't really help solve this.
You’re always making tradeoffs. For 100 sessions , which one works better ? Would you use the worse setup for the once a month you need to reboot ?
I built an almost the same thing for myself and the main use case for me is on a work laptop where I run WSL and I leave on standby overnight. Then the I'd dept forces a reboot to install updates and all my windows are gone...
Saving state every afternoon would be a pain.
Move it to hyperv . Windows terminal integrates as cleanly as wsl . Hyperv gives you hibernation by default
Might be a bit naïve, but wouldn't a VM take up a lot more memory?
You can get the overhead down to 85mb, about an empty browser tab