This is probably a good example of the opposite. It would be a mistake to design for the fleetingly rare case. If you’re dealing with a handful of extensions, a json file that’s rewritten is fine.
replyBut the software already has multiple database systems built in. There's not exactly overhead to use what plumbing is already there, instead of writing to disk.
replyFirefox is absolutely abysmal at not corrupting its JSON stores, too. I've had it crash and lose tabs so many times. Perhaps moving back to SQLite wouldn't be a bad idea.
replyI had to recover somebody's bookmarks for them recently after it decided to destroy the main copy.
> I had to recover somebody's bookmarks for them recently after it decided to destroy the main copy.
reply@Chaosvex curious how you did that.
Thankfully, it makes backups inside the profile folder and has a bookmarks file import option that'll accept them.
replyIt does the same for session tabs (minus the import options) but that never seems to actually work.
In an ideal world, software with 100 million users would be optimised for energy usage. It all adds up. This does pale in comparison to everything else, though.
replydeleted
reply