Quote:
Originally Posted by eschwartz
I have never had the Kindle UI slow down except for when creating collections and doing a global search.
Not sure about the collections management. Fortunately the one thing I spend the least time on is editing collections. 
The global search is a no-brainer that it is slow.
On the other hand, I have borrowed my friend's Nook Glowlight -- for purely experimental reasons!!! -- and discovered it to be slow in every way shape and form.
The Nook also suffers from a severe lack of storage space, e.g. partitioned userstore and the removal of the exalted SD slot. 
"i think it generates an index file when you add/subtract books and uses that to point to files instead of going to the actual files.this makes it fast." -- what exactly is this even supposed to mean? Do you mean to imply you think the Kindle loads the ebook file into memory in order to page through your device library? I cannot fathom why you would think so, and considering the Kindle only has 256 MB of RAM, it could not possibly load 3 GB of books into memory just to show the books ondevice. 
Suffice it to say -- both the Kindle and Nook store metadata about the book i order to index it.
I do not have a Kobo, but I have never had problems with the speed of transfer to my Kindle. Since it is a basic filesystem operation, I don't see what might be going wrong.
Although calibre must update the Kobo database in addition to transferring the book, so if anything it would be the other way around (by milliseconds  ). |
I am not talking about the nook glowlight without the sd card slot which is just awful because it has no sd card slot and looks wise.
i am talking about the one before which was awesome and did not suffer the slow down you mentioned.
256 mb memory does not load all the books but caches them in the kindle and slows because of it.
the original nook generated an index text file instead with pointers to the actual file and was very fast.
i have 3 to prove it.