I call this "criticizing something without understanding why it succeeded in the first place". Also "writing blog posts while blind to other users' use cases".

I call this "criticizing something without understanding why it succeeded in the first place". Also "writing blog posts while blind to other users' use cases". Do you really think there were no other "portable" formats to exchange data and SQLite is the first one? The reason CSV is so popular has nothing to do with technical superiority which it obviously lacks. The reason CSV is so popular is because it is dead simple and extremely easy to integrate within practically any conceivable workflow. And because it is text format which you can trust, even if you have no other tools, you can inspect and edit in a text editor which is exactly the reason why other formats like INI, XML, JSON or YAML are so popular. How would you: a) Run shell command on a locked (can't install anything) PROD server to find the files and write a report of the file location, date of change and file size so that it can be easily processed by something else? Return the data in stream on the same SSH connection? b) Quickly add a line to an existing startup script to get a report of when the script is starting and stopping so you can import data to excel. You just need it for couple of days, then you delete it. c) Produce a report you can send to your coworker knowing they don't know how to program? And you don't want spending time explaining to them how to make use of your superior file format? d) You talk to another team. You need to propose a format and specify a report with as little effort as possible. You know they are not advanced technically so you keep things simple? e) You are solving an emergency and have to cross-check some data with another team. You need to produce a file that they will be able to read and process. You are stressed for time so you don't want to start a committee right now to find out shared technology. What would be safe choice without asking the other team for options? f) A manager asked you for some data. You want to earn quick kudos. How will you send the data to get your kudos rather than irritating him? These are all real life situations where CSV is being used. As much as I understand technical arguments for SQLite, not every person is a developer. And all that technical superiority is worth nothing when they struggle to make use of the file you sent them. I would say, the news of CSV's death are greatly exaggerated.