3 ms·
While they look cool am I the only one who thinks that if you need to display a "Loading" spinner you should rethink what it is you're doing? Maybe I'm just tra
by kenrikm 13y ago
While they look cool am I the only one who thinks that if you need to display a "Loading" spinner you should rethink what it is you're doing? Maybe I'm just traumatized from the surge of Flash based sites back in the day (thank god flash is on the way to the grave)
- zachlatta 13y agoFinally! Someone who has the same opinion on this as me! I can see where spinners can be useful, but we need to remember that we killed Flash for a reason. What's wonderful about the web is the ease of distribution. As I see more and more spinners, I'm becoming increasingly worried that the standards will become the new Flash. For an example of a website that bothers the hell out of me with it's loading is Blogspot.
- hmottestad 13y agoLoading doesn't have to mean "this page is loading a huge pile of crap that you don't want". It could simply mean "you don't need to press that button again, we really have sent your request, it's just taking a second". Examples that are useful: - Credit card processing (always seems to take 2-3 seconds) - Big database query (searching maybe. But don't do this in regular webapps, just in those where the user expects the query to take some time, like in enterprise apps). - Uploading or downloading a small file that takes a few seconds (instead of a progress bar that is misleading on small files) - Buffering audio/video
- alekseyk 13y agoIf you can architect an extremely fast platform that has absolutely no delays for any of the operations at any given moment then you can throw things around like 'rethink what is is you're doing'. My guess is that you can't.