|
I tend to usually side with practicality, but I can understand the need for a lot of material on one device if it's reference material. You may not need it every day, but when you do, you do. The simple fact of the matter is that a properly implemented system should be able to function with a great number of books, at least as many as might be expected to fit on the maximum storage the device claims to be able to access. If they cleaned up the database/code it should be quite possible on any Kobo device. I don't keep a lot of books on my Kobo devices, just a few hundred, but it should be possible for Kobo to process contents and maintain a database without huge delays.
They could restrict new books being copied to just one folder and force deletions to be done only through the database to remove the need to scan for new books and deletions in order to update the database en masse on startups. That alone should remove much of the bottleneck and delay complained of by people with large collections. Background processing might help a lot too, or at least offer the option of processing certain folders first and let the user select a title to read from them and continue processing in the background. Long delays kill any device in the eyes of the user.
|