Comments on: File synchronizers suck! Guess what, I’m procrastinating! http://www.sixproducts.com/25/file-synchronizers-suck-guess-what-im-procrastinating/ Can you build a self-sufficient Micro-ISV in one year? Wed, 07 Jan 2009 02:27:04 +0000 http://wordpress.org/?v=2.3.3 By: Endolith http://www.sixproducts.com/25/file-synchronizers-suck-guess-what-im-procrastinating/#comment-191 Endolith Thu, 03 Apr 2008 15:22:53 +0000 http://www.sixproducts.com/25/file-synchronizers-suck-guess-what-im-procrastinating/#comment-191 You might be interested in this article I wrote. Only tangentially related, but your "process hibernation" reminded me of it. Instead of saving the memory state of the entire program, it is more document-centric and continuously saves the state of the document itself, so that closing a program and minimizing a program are really the same thing. http://endolith.com/wordpress/2007/12/24/abolish-the-saving-of-documents/ Your post brings up an important point about the state of the program changing when you restart it though. (In a graphics program, for instance, you might have the eraser tool selected. When you minimize it and reopen it, the eraser tool is still selected, but when you close it and re-open it, it goes back to the default brush tool. In other types of programs, this volatility might cause more serious problems that I hadn't thought of. Even with the graphics program constantly resetting, it would cause a little lost time as you re-select the tool you were using last time you had the document open. And if the graphics program remembered its state from one instance to another, but you open a different document each time, that would cause wasted time, as well. Should the state of the program be saved along with the document?) You might be interested in this article I wrote. Only tangentially related, but your “process hibernation” reminded me of it. Instead of saving the memory state of the entire program, it is more document-centric and continuously saves the state of the document itself, so that closing a program and minimizing a program are really the same thing.

http://endolith.com/wordpress/2007/12/24/abolish-the-saving-of-documents/

Your post brings up an important point about the state of the program changing when you restart it though. (In a graphics program, for instance, you might have the eraser tool selected. When you minimize it and reopen it, the eraser tool is still selected, but when you close it and re-open it, it goes back to the default brush tool. In other types of programs, this volatility might cause more serious problems that I hadn’t thought of. Even with the graphics program constantly resetting, it would cause a little lost time as you re-select the tool you were using last time you had the document open. And if the graphics program remembered its state from one instance to another, but you open a different document each time, that would cause wasted time, as well. Should the state of the program be saved along with the document?)

]]> By: blackkat http://www.sixproducts.com/25/file-synchronizers-suck-guess-what-im-procrastinating/#comment-35 blackkat Fri, 02 Nov 2007 18:46:32 +0000 http://www.sixproducts.com/25/file-synchronizers-suck-guess-what-im-procrastinating/#comment-35 There used to be a hardware device out there that allows you to bring your environment with you, and to hibernate the current state back to the device. Unfortunately it seems like its no longer available :( News here: http://www.linuxdevices.com/news/NS8562564746.html There used to be a hardware device out there that allows you to bring your environment with you, and to hibernate the current state back to the device. Unfortunately it seems like its no longer available :(

News here:
http://www.linuxdevices.com/news/NS8562564746.html

]]>