Quote:
Originally Posted by Ken Maltby
My first Kobo was the AuraHD, it was not my first ereader though. I do not like the database approach to book management vs. a file manager approach. I do not like the "Rewards" and other marketing efforts. I do not like the data gathering done for both Kobo and Google Analitics.
I DO like that, at least originally, much of the software was implemented in human readable scripting language. I DO like that they came out with the highest resolution ereader available. Another thing I DO like is that I need not depend on the Kobo supplied User Interface or their reading software. Thanks to the folks at Github, a number of whom post here. Plus a few others posting here who are independent of the Koreader Github project.
From my point of view, the near perfection of the Kobo AuraHD (for my use), is not totally, perhaps not even largely, something to credit Kobo with.
Luck;
Ken
|
Again, making the point, is there's nothing inhernetly "wrong" or "buggy" about their approach. They make no attempt to hide that the reader navigation is through a metadata-based approach, which by definition requires a database to manage the metadata, and the system they've designed to do that works pretty well.
You may prefer otherwise, but the device works well in how it was designed.
Personally, I prefer the metadata based approach. It allows me to slice a cross-section of my library in multiple ways instead of being locked into a rigid file-based structure. With the database I can look at books by author, series, genre, or any other criteria I'd like. It allows me to group and find books through multiple parameters quickly and easily.
I'm sure, to some degree, there's also an age-related bias towards one or the other. While I'm young enough to have decent experience with file managers, autoexec.bat and himem.sys, the benefits presented by a "Library" approach based on metadata have won me over and I couldn't care less where files end up (that being said, I have Calibre organizing my books by author through the file structure on the reader).