|
Not going to vote on this, because that's silly. But I have to agree that the single biggest annoyance is the database getting involved unnecessarily.
If you can't parse a file, that's fine. Reject it transparently. But there's no reason for a single malformatted ebook to make the whole device almost unusable. I've spent way too much time fixing books to prevent the database from choking.
That said, I haven't seen database choking in 2.5.2. Not sure whether they actually modified something, or whether I've finally koboified my books and reading habits.
|