4 ms·
I don't like this because in practice sites usually fail to re-enable the submit button if something goes wrong. Just let the user submit multiple requests if t
by digitaLandscape 8y ago
I don't like this because in practice sites usually fail to re-enable the submit button if something goes wrong. Just let the user submit multiple requests if they want to retry, don't take that away from them, just make it harmless.
- jen729w 8y agoNewbie programmer here, but even I am already implementing finite state machines which handily fix this sort of issue. Any sort of UI without them now feels archaic.
- hood_syntax 8y agoAgree 100%. If you don't have explicit state transitions in a UI, you're asking for trouble. I think some people don't realize how much harder they make it on themselves by not setting clear boundaries; they see the up front cost and balk, when it saves a non-trivial amount of headache in the future, not to mention reducing mental overhead when you've got the structure hashed out.
- digitaLandscape 8y agoMeh. The logic still applies: on a bad network, the first request can hang for half a minute when a retry would get lucky and go through immediately. Don't handcuff your users for no benefit, just because you can't write a well-behaved backend.