4 ms·
If you can reliably break down your complex flow into a tree of checkboxes, you could just as easily render a truthful progress bar based upon how many sub task
by admax88q 6y ago
If you can reliably break down your complex flow into a tree of checkboxes, you could just as easily render a truthful progress bar based upon how many sub tasks are done.
- eru 6y agoYes, but that bar would still get hung intermittently whenever a specific task took a long time.
- karottenreibe 6y agoHow is the checkbox thing any different? If one task blocks progress, the tree also doesn't update
- eru 6y agoI don't know whether it _will_ be any different, but there was some speculation about that: > If the users can see the detailed tasks, maybe they will be less ticked off by a jumpy progress bar.
- TeMPOraL 6y agoContext. You see not just the thing currently executing, but also the things remaining to be executed - which allows you to mentally gauge which of them may slow down.
- coldtea 6y agoAt least I know what it is doing at the moment its blocked (and in many cases I can tell whether that is justified to take N time or not). With a progress bar I don't know anything.