https://bugs.kde.org/show_bug.cgi?id=438317
James Tuttle <jwtut...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwtut...@gmail.com
--- Comment #8 from James Tuttle <jwtut...@gmail.com> ---
As a user new to Digikam, I find the "download at first launch" to be pretty
poor UX, all things considered.
If these components really are core features of Digikam (and I think they are),
then they should be packaged into the Digikam installer. The built-in
downloader doesn't seem to work very well (I am having trouble getting it to
not continually try to download from non-functional KDE mirrors) and seems like
a case of misplaced optimization.
Bandwidth is cheap. Users' time is expensive. I have already spent far more
time sitting in front of my computer, continually clicking on "Try Again", than
it would have taken just to include these extra files in the core installer
that I downloaded when I decided I wanted to try Digikam. To save someone some
theoretical bandwidth when upgrading, the process has instead wasted my time.
This doesn't seem great.
Furthermore, it's not even clear to me that this design actually saves
bandwidth. It does in one particular case (that of upgrades, apparently), but
would be strongly counterproductive if you were, say, installing a whole lab's
worth of computers with Digikam. There, you'd want to download the installer
once, distribute it locally, and install it on each machine. Having each
machine then go online and download the same files over and over isn't great. I
suspect a case like this (where the installer is passed around locally via
removable media, file shares, etc.) is pretty common in low-bandwidth
environments.
It's annoying and a poor introduction to Digikam for new users, wastes human
time, isn't especially reliable, and the benefit to users with
limited-bandwidth connections seems arguable at best. Definite misfeature, IMO.
--
You are receiving this mail because:
You are watching all bug changes.
