Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 20
    This is justified by the fact that successful operation is much more likely, therefore being slow just to avoid the rare case of over-optimistic feedback is a bad trade-off. Transposed to personal relationships, would you rather interact with a calm, sunny person or one who categorically assumes that everything that can go wrong will go wrong and acts accordingly? Commented Jan 31, 2013 at 15:54
  • 1
    For me, what I'm struggling with, is that a desktop application has both the operation and error happen immediately. Where as, with web applications the operation happens immediately, but the error is lagged. Yet, sites operate with the design of a desktop application. Commented Jan 31, 2013 at 15:57
  • 7
    Have you also considered what happens when your desktop application writes to disk, it actually goes into an OS buffer, and the disk fails before it could be written to the platter? Or, for that matter, the disk fails after the bytes are written to the platter. In both cases, the user thinks that something has happened when it really hasn't. Commented Jan 31, 2013 at 16:02
  • 2
    @KilianFoth I'd prefer the one who assumes everything can go wrong, if the "sunny" person is going to punch you and steal your wallet at the first sign of trouble. So it depends on the scale of the page's reaction on failure. Commented Feb 1, 2013 at 3:55
  • 1
    @ButtleButkus I think those saving messages are new. They weren't there when I asked the question. I've notice google adding more feedback lately that's it's doing stuff in the background. Commented Nov 5, 2014 at 13:11