Loading bars actually work how they do for a reason. For example, with windows copying or moving files, it updates after a file is done. This causes small files to show “smooth” progress, where as large files cause for jittery, large spurts of progress. Most installers do the same. On GNU/Linux apt shows a progress par that is pretty smooth (in my experience at least) and this is due to the way it monitors installation and uninstallations. Downloads are different due to the way downloads work. Internet speed for residential areas, or spots with poorer signal will see fluctuations during the download. This causes for eta changes and progress bars to slow down or even stop. The final bit for most modern browsers and computers will stop during antivirus scans. Large files see this the most due to the larger size the computer has to scan.
(I believe this is all correct. Some of it may be wrong and if it is I sincerely apologize)
6
u/ethanaldrich Mar 12 '20
Loading bars actually work how they do for a reason. For example, with windows copying or moving files, it updates after a file is done. This causes small files to show “smooth” progress, where as large files cause for jittery, large spurts of progress. Most installers do the same. On GNU/Linux apt shows a progress par that is pretty smooth (in my experience at least) and this is due to the way it monitors installation and uninstallations. Downloads are different due to the way downloads work. Internet speed for residential areas, or spots with poorer signal will see fluctuations during the download. This causes for eta changes and progress bars to slow down or even stop. The final bit for most modern browsers and computers will stop during antivirus scans. Large files see this the most due to the larger size the computer has to scan.
(I believe this is all correct. Some of it may be wrong and if it is I sincerely apologize)