True (in most contexts, probably including this one), but I think that only makes the case for SQLite stronger. What people do still care about is a good flexible, usable and reliable interface. I’m not sure how to get that with YAML.

I think SQLite is a great middle ground. It saves the database as a single .db file, and can do everything an SQL database can do. Querying for data is a lot more flexible and a lot faster. The tools for manipulating the data in any way you want are very good and very robust.

However, I’m not sure how it would affect file size. It might be smaller because JSON/YAML wastes a lot of characters on redundant information (field names) and storing numbers as text, which the database would store as binary data in a defined structure. On the other hand, extra space is used to make common SQL operations happen much faster using fancy data structures. I don’t know which effect is greater so file size could be bigger or smaller.

Sure, it would have, but I was following the time-honored tradition of reading only the title and the Lemmy comments without clicking through to the full article. If that comment hadn’t been there, it is possible that my intrigue and confusion would have been sufficient to make me betray my legacy and bring shame to my family by actually reading the linked article. Disaster avoided!

Oh, thanks, I needed that to understand what this was talking about.

I definitely do for quick scripts, but I try to break this habit. The biggest advantage of def main() is that variables are local and not accessible to other functions defined in the same script, which can sometimes help catch bugs or typos.

sqlite is technically just one C source file, so that’s definitely a script.