Thanks for the condescension. It would be fairly simple to keep a redundant backup of the previous session file. A world view which puts that onus entirely on the user and not of the product is exactly what is wrong with software engineering these days. No one should need to use a backup except in case of hard drive failure, and with proper hardware that should not be an issue either. The point is NOT to build the sexiest program possible and patch holes in it weekly. The point is to build something reliable. And yes, everything can fail at some point but handling a fairly common error with a small amount of data would be -- professional. Heck, why is there no backup of the previous state for when you hose an "update"?
Enjoy your clique. I'm gone.