[jraph]

> Sqlite is good, but a database is simply unnecessary in many cases, because filesystems are very optimized and perfectly useable for many cases. This encourages hacking and interoperation. I could comfortably browse through my bookmarks in a mature native file system explorer of my preference, instead of struggling with a tricky scrolling menu within a browser

SQLite is very good indeed. It's fast and offers a nice querying API. You can use SQLitebrowser if you want to browse this data outside the browser UI, and we could always have a FUSE filesystem for sqlite database if we really wanted to be able to browse this data with a file manager. Since SQLite is used everywhere, the effort would be shared. One of the many good things about SQLite is that it is (de-facto) standard, way more than regular configuration files.

> Systemd: Binary log files. I should be able to configure my system with `sed` and `awk` scripts that easily modify text configuration files.

Configuration files are still regular text files, and are way easier / simpler than before systemd / upstart. You are also a command away from having a text representation of the logs, and that's journalctl, which can be piped into the regular unix tools, so I have not found an actual situation where it matters.