Why some apps use fake progress bars (2017)

Re:Why some apps use fake progress bars (2017) by JustSomeNobody on Friday February 02, 2018 @07:43PM (#16295421)

Ages ago I evaluated some reporting software. We were using Crystal Reports at the time. One thing that CR did better than the others was make pages available as they were generated. This made the software feel faster even though it was slower than one or two of the others[0] at the time.

[0] Can't remember which ones exactly.

[ Parent | on HN ]

Re:Why some apps use fake progress bars (2017) by starsinspace on Saturday February 03, 2018 @05:38AM (#16297071)

For interactive applications, reponsiveness trumps raw throughput. It's what made operating systems like AmigaOS and BeOS so fast: they didn't actually crunch numbers faster, but they always stayed responsive and quickly reacted to user input under any load, that made them feel faster.

[ Parent | on HN ]

Re:Why some apps use fake progress bars (2017) by ams6110 on Friday February 02, 2018 @08:33PM (#16295607)

Just had a little PTSD flashback moment there at seeing the words "Crystal Reports"

[ Parent | on HN ]

Re:Why some apps use fake progress bars (2017) by sundvor on Saturday February 03, 2018 @05:31AM (#16297057)

Oh dear. That garbage came with Cold Fusion (before it became ColdFusion), IIRC.

[ Parent | on HN ]

Re:Why some apps use fake progress bars (2017) by supergreg on Friday February 02, 2018 @08:33PM (#16295608)

Which is why browsers take so seriously the time to first paint despite the efforts by javascript frameworks to push it back.

[ Parent | on HN ]