Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
AtuM28838dAre you 110%? 🤪
Protip: Never ever let the progress bar reach 100% before the task is actually fully done - including whatever tiny "cleanup" and "registration" stuff needs to be done after, for example, installing software.
Let it get to 99%, then do all that negligible stuff and jump to 100% at displaying the complete message.
Always round progress percentages down.
sariel7418dI always calculate my loading bars based on 8-bit math so that every loading bar has a max value of 256.
So, I guess that means you might need to wait for 256% compete?
Yup. Sometimes progress bars are being used to indicate indefinite loading. They fill quickly in the beginning and are getting slower and slower afterwards. Never reaching 100%.
This sucks. Because we already have a UI concept for indefinite loading: a spinner. I guess it‘s just some designer who finds it cool. I wouldn’t expect a dev to do such things.
@Lensflare I was once told to implement a fake progress bar that displays a function converging to 1 over time and when the task is complete it turns into a polynomial matched to both the current value and rate of change as well as some tuneable rate of change at the value of 1 within some short timeframe. The result is that the line slows down as it fills up, and then accelerates without jumping once the task is done.
It was the most elaborate mathematical scam I've ever seen and it destroyed my trust in progress reports forever.
This rant wasn't satisfying enough. Who the fuck makes things take longer than 100% with no indication of what's happening?