While I know that Discovery is not everyone's favorite program, I feel it has a use and is part of the general getting-away from the terminal, which is the geekiest part of Linux. The main graphical program managers, Muon and Synaptic, are not for beginners or casual users. So Discovery should be a good alternative, in theory. I use it mainly for updating, and it's doing a better job than before through the addition of a general tasks bar graph, which shows the progress of the updating. But I still can't figure out what Discovery's programmers mean to communicate by the use of the individual program progress bar charts. At 49% of progress the updates are all downloaded, but the bar graphs show a chaotic view of progress, with some programs almost completely downloaded while others haven't even started. The second phase, which finishes at roughly 79%, shows all the other bar graphs catching up until they're all lined up neatly at 75% progress. What happens next is weird. Instead of advancing ever closer to 100%, the bar graphs instead start receding to about 50% progress, only to disappear in a flash when the general update is finished. What is the logic here?
Most other Linux distros I've looked at have functional bar graphs showing each stage of the update process. If Discovery's programmers can't do the same, then they should eliminate the individual graphs entirely and let the main one show the progress. But it seems to me that they should know how to do this right.
Most other Linux distros I've looked at have functional bar graphs showing each stage of the update process. If Discovery's programmers can't do the same, then they should eliminate the individual graphs entirely and let the main one show the progress. But it seems to me that they should know how to do this right.
Comment