> The real need for a database isn't bookmarks, it's history.
The real need for a database isn't history either. It is extensions. You can have a custom
format for history so that given an URL you know whether it is in it or not, and you can list
all of them in the order of time. Easy. But extension is different. You don't really know
what they need, because each of them need different thing. So your only option is to ship
something really generic, in other words, database. If they have to ship a database anyway, I
don't see any reason they are not merging bookmarks and history into the same framework.