question before I buy

[guma]

Originally Posted by filmo

5,000 books on a kobo Touch? Comments by someone that has done this. What firmware version are you using? Problems?

It might work somehow but, from my experience, putting more than ca. 1000 books on the main memory will slow down the device significantly.
Various firmware versions will give you different results most likely ... but I doubt that you'll find a firmware that will cope well with 5000 books.

[guma]

Originally Posted by CypressTiger

Can I open pdf, epub, txt, and html?

Yes, but chances are you will not like what you get when you open a pdf on a KOBO device ... The other formats should work fairly well (with a few rendering idiosyncrasies that may or may not bother you).

Originally Posted by CypressTiger

Can I use my own folder organization system?

Nope. If you are not willing to use a metadata/tag based approach to organize your ebooks (with, e.g. something like calibre) look elsewhere and don't buy a KOBO device.

[filmo]

I totally agree about very poor performance with more than 1000 books in library. The performance with many books on shelves is improved a little compared to Kobo's first version but still irritating slow to impractical. I know from experience with Sony T1 not displaying covers in large library lets navigating library remain snappy. Sony knew this was the cure for stuck can't sort and load cover images in large library. How many different size cover images for each book does Kobo firmware store, catalog, and display?

[TonyToews]

As far as the 5000 books go only put a few dozen books on the device at a time using the Calibre software. I have four or five hundred books but really that's kinda awkward to deal with. And use Calibre or your computers file system to manage your library.

[jackastor]

Originally Posted by filmo

I totally agree about very poor performance with more than 1000 books in library. The performance with many books on shelves is improved a little compared to Kobo's first version but still irritating slow to impractical. I know from experience with Sony T1 not displaying covers in large library lets navigating library remain snappy. Sony knew this was the cure for stuck can't sort and load cover images in large library. How many different size cover images for each book does Kobo firmware store, catalog, and display?

There is no performance issues with large amounts of books. You open the book you read for a few minutes and turn a page, no problem with performance at all. Its an ereader not a tablet computer nor should one think of it as anything other then a book. That's what it was designed for that's what it does and it does it very well. You want faster performance then you need to buy a full flegged computer or tablet an ereader is not for those who want speed.

[Lyn2012]

Originally Posted by jackastor

There is no performance issues with large amounts of books. You open the book you read for a few minutes and turn a page, no problem with performance at all. Its an ereader not a tablet computer nor should one think of it as anything other then a book. That's what it was designed for that's what it does and it does it very well. You want faster performance then you need to buy a full flegged computer or tablet an ereader is not for those who want speed.

Personally I do want performance from my ereader, and would be happy to pay slightly more for a faster processor and more RAM, if that is what it takes. If an ereader is quoted as able to store a library of ?,000 books, them IMO it should also be able to respond immediately when browsing or searching the library or any other book related activity. If my device isn't as fast as my phone for example, then I am not satisfied with it. This is the reason my whole library is never on my reader, for me, responsiveness is more important. I don't require a tablet as I prefer e-ink and have no need for any internet access, just a standalone responsive reader.

[jackastor]

Originally Posted by Lyn2012

Personally I do want performance from my ereader, and would be happy to pay slightly more for a faster processor and more RAM, if that is what it takes. If an ereader is quoted as able to store a library of ?,000 books, them IMO it should also be able to respond immediately when browsing or searching the library or any other book related activity. If my device isn't as fast as my phone for example, then I am not satisfied with it. This is the reason my whole library is never on my reader, for me, responsiveness is more important. I don't require a tablet as I prefer e-ink and have no need for any internet access, just a standalone responsive reader.

You forget the os is a limited Linux environment designed to foster reading. When I search through my 4800 ebooks to find a particular title its fast and responsive. When I decide to visit my shelves it takes a about 1 to 2 mins to bring them up because the Kobo does not create or save a search index such as a windows, android and apple device does (tablet or Computer). Instead it has to generate it on the fly. The best guess as to why Kobo did not implement it would be space saving. You use an ereader for reading that's a specific use and its all its designed for. IF you want speed such as your quad core phone or tablet then use those devices they are built to be multi use devices... also the cost hundreds of dollars for such devices ensure you get the speed and performance you desire. For 150 bucks or less you get an ereader for the specific purpose of reading nothing more nothing less it does what its designed to do and only do. And yes it does it very well as is to be expected.

Increase in performance speed = less battery life usually 10 hours at best of use vs 2 months of use. You decide what you wish to sacrifice. That said I guess it boils down to this. Some of us require speed and some of us like to relax and enjoy the scenery. Bottom line I think is we will have to agree to disagree and respect the opinions that we both support.

Regardless you have a right to desire what you wish for and I will simply have to respect that

Regards

JAck