3 ms·
It wasn't reliable back then, but that was nearly ten years ago. I'm sure it's improved since then. And honestly, it could have been just one regression that wa
by morganvachon 9y ago
It wasn't reliable back then, but that was nearly ten years ago. I'm sure it's improved since then. And honestly, it could have been just one regression that was soon fixed, but I had already moved on and I generally don't look back when something like that happens.
- colanderman 9y agoRight – "fixed the bug that ate my files" isn't good enough. I need to feel confident that the next version of the software won't introduce another similar bug. The best "protection" I've seen in this space is to log all changes to the edited document, through a simple (and therefore easy to prove correct) code path. The only editor I've ever seen do this was a Xilinx schematic editor. The editor crashed all the time, but I never lost work, since on restart, the editor simply replayed what it had in its log. (This was fun to watch!) Of course this method isn't foolproof, but it went a long way making me feel confident my work wouldn't be lost.