It's not only "writing" though. It's "writing" AND "reading". Can you read the correct line in in CSV faster? Can you find the row with specific critiria like

It's not only "writing" though. It's "writing" AND "reading". Can you read the correct line in in CSV faster? Can you find the row with specific critiria like SQLite faster? Can you handle concurrency correctly like SQLite? Can you make sure your CSV is always in consistent state like SQLite? The point of the article is that SQLite is still fast even with all the benefit of database. The idea of SQLite is that you could default to using it, and move away when it hits its limit. Nobody should default to using CSV, you use CSV when you have to, despite all its limitation.