Hacker News Reader

One thing I've never understood is the confirmation dialogue you get when closing an application. Of course I want to save the document! The only time wouldn't want to save my changes is when I want to revert all the changes I made this session. I already have a perfectly good button for that the, undo button. (at least in a perfect world).

View on HN

You don't ever run into that accidental situation where you opened a doc/makefile/source/etc that you just wanted to view but not change? That dialog is handy when you accidentally made a change but weren't aware of it. It doesn't happen a lot, but I know I'd have a number of more random characters in documents than I have now.

I think unlimited undo would solve this situation. If you're autosaving revisions, it's not a huge step to imagine allowing undo across application invocations.

+1. You could make the default "X" button mean "save and close", and have a separate button (perhaps in the drop-down menus, since this action is rare) mean "save and close".

Exactly. The dialog is based on the assumption that both options are equally likely to be used. That's simply not true. A user might click no but will almost always click yes. A dialog that almost always receives the same answer should be eliminated.

Reply on news.ycombinator.com