Live data from Hacker News

Why some apps use fake progress bars (2017)

theatlantic.com

131–140 of 200 posts

Re: Why some apps use fake progress bars (2017)

#131

In a similar vein, there's this website: http://haspvsnpbeensolved.com/ Although; in this case; I'd hesitate to call this a strict example of 'benevolent deception'. ;)

Almost nine thousand lines of Javascript to show a fake loading screen for a few seconds...

Re: Why some apps use fake progress bars (2017)

#132

Earlier quoted context omitted.

I am reminded of a webcomic, that i fail to locate at this moment, that reminded me of the practice of placing something next to a progress bar, like say during a Windows 95 install, to check if anything is actually happening.

This is the comic you're thinking of. http://www.commitstrip.com/en/2015/02/19/when-i-install-a-so... This was one of the comics that convinced me to add them to my RSS feed. I have not been disappointed since.

I removed them from same recently because I felt I could no longer relate to the jokes, or some such.

Re: Why some apps use fake progress bars (2017)

#133

Earlier quoted context omitted.

I am reminded of a webcomic, that i fail to locate at this moment, that reminded me of the practice of placing something next to a progress bar, like say during a Windows 95 install, to check if anything is actually happening.

I do that whenever I have to wait on a progress bar. I zoom in with whatever accessibility options there are, then when a pixel is 3-5mm I put my mouse cursor at the end of the bar and wait.

I don't use the zoom, but yeah, parking the cursor right at the progress bar to see if it's advanced is useful if only to amuse myself. :)

Re: Why some apps use fake progress bars (2017)

#134

Two mobile devices I worked on, at different companies, ended up with fake progress bars for boot-up. We engineers wanted individual bar segments for kernel load, filesystem mount, daemon startup and so on -- but wiring up the necessary instrumentation to the GUI would have been significant work, and management wasn't going to allow anything less than a show-stopper bug to delay code freeze. So in the real world, tim…

Just show me the console log...

Re: Why some apps use fake progress bars (2017)

#137
post #16

Earlier quoted context omitted.

Visual confirmation that it isn't hung, I'd be happy too.

You're happy until 30 minutes later when the progress bar is still getting asymptotically closer to the end, and you come to suspect that the only thing that didn't crash was the progress bar.

>when the progress bar is still getting asymptotically closer to the end

That, my friend, is an impressive command of the English language.

Thank you for teaching me the word asymptotically! [0]

http://www.dictionary.com/browse/asymptotically

Re: Why some apps use fake progress bars (2017)

#138

Reminds me of the old IE bar (not sure if it still does this), but it would crawl towards 100%, getting slower and slower as it approached the end, when waiting for a page to respond. In reality IE had no idea how much "progress" had been made by the server, if any.

Same as Explorer, the file browser. Once you know, it's useful as a timeout meter, i.e. it signals "how long before this device/network location is deemed unreadable".

Wouldn't an actual timeout timer be more useful, like when Ubuntu is booting/shutdowning it gives a "job is trying to complete" message and a 90s (say) timer before it ignores it and carries on.

Windows updates could use this, when it randomly decides to wait 30 minutes on startup despite not warning you and not giving a skip option.

Re: Why some apps use fake progress bars (2017)

#139

Earlier quoted context omitted.

That is one thing I dislike about sites that show no loading bar. On a slow connection it's impossible to tell if the page is still loading or already failed. Web browsers have progress bars. I think your complaint is with "sites" that just serve a JS payload and then load "the real site" entirely from requests made by JS. Turns out if you generate and serve actual HTML, you get a progress bar for free!

I don't know why every thread about Web applications needs someone to tell me that technically HTML was just designed to be a document format. OK, great, now it isn't just that.

That’s true, but I can mention several online stores that do this. Even on a good network the site remains blank for seconds at times. If they at least served me a logo I’d know the site wasn’t dead!

Re: Why some apps use fake progress bars (2017)

#140

Earlier quoted context omitted.

That is one thing I dislike about sites that show no loading bar. On a slow connection it's impossible to tell if the page is still loading or already failed. Web browsers have progress bars. I think your complaint is with "sites" that just serve a JS payload and then load "the real site" entirely from requests made by JS. Turns out if you generate and serve actual HTML, you get a progress bar for free!

I don't know why every thread about Web applications needs someone to tell me that technically HTML was just designed to be a document format. OK, great, now it isn't just that.

First someone states that the way web sites work now sucks. Then the next person states, ‘Well we used to build sites this way and then it doesn’t suck’. And then the next person comes in saying ‘well that just isn’t the way we build sites now’.

If that isn’t the way we build sites now, either change the way we build sites or accept that it sucks. But this is Hacker News so we’re supposed to think about different ways to build sites than what we do now.

Post reply on HN