> We hide most of that implementation detail from the user because it's non-essential to the task at hand.
and then you have tons of security holes and bugs. Remember when browsers thought it was nice to hide loading from the user, and every site had to add "do not click submit twice" and such? what's next? one page apps relying on a share button and then having to write "do not share via the hidden URL"? ...google maps was like that for ages now that i think of that...
We should be coming up with ways to make information denser and more meaningful. not scarcer.
"Do not click submit twice" isn't a side-effect of hiding loading; it's a side-effect of sites taking something that should be idempotent (a single purchasing transaction) and failing to code it to be idempotent. Nothing about the page loading UI would have prevented that issue.
and then you have tons of security holes and bugs. Remember when browsers thought it was nice to hide loading from the user, and every site had to add "do not click submit twice" and such? what's next? one page apps relying on a share button and then having to write "do not share via the hidden URL"? ...google maps was like that for ages now that i think of that...
We should be coming up with ways to make information denser and more meaningful. not scarcer.