"Instead of keeping your work safe, I've been stacking it up on the edge of this incinerator for the past hour. Now, are you ABSOLUTELY SURE you don't want to incinerate it all? Last chance!"pic.twitter.com/dAgftlazcJ
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
"Instead of keeping your work safe, I've been stacking it up on the edge of this incinerator for the past hour. Now, are you ABSOLUTELY SURE you don't want to incinerate it all? Last chance!"pic.twitter.com/dAgftlazcJ
Making it so that hitting Save trashes your undo history is another absolutely indefensible design decision in desktop softwarehttps://twitter.com/HorseboyTFE/status/1238762876871081985 …
Because writing it out to the floppy will take like 15 seconds and the computer can't do anything else in the meantime.
When I started working, my mentor would edit the database frontend live. Every save was a commit to production. I didn't do it 'cause I didn't have the trigger discipline on Ctrl+S
Yeah, I'm at the point where most software I use recovers files if closed suddenly etc. But it's still not seamless. It doesn't just, always save, and have a decent undo, and restart in the same place. This is one way apps UI is much better than applications
If people need a manual save, it can save the current edit state, so if you close it it opens in the same point with the "unsaved" data and let's you revert to the "saved" version if you want.
In the 80s, Borland had a word processor "Sprint" that kept a near-real-time keystrokes log. In the event of a crash, it would recover the editor state very closely to the last action or even fully. Saving to a file was separate, though. I liked it, but it didn't catch on.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.