Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[flagged]


Your alternative is... what exactly? A unique and baroque file format for each application (see: Git)? Folders of JSON or markdown files which are slow, easily corrupted, and lack indexing? Depend on some memory-heavy external DB service like Postgres?

In most cases, embedding SQLite is the best solution. And that is exactly what it was designed for.


If you only knew how much SQLite is used...

* Apple Mail ( "~/Library/Mail/V5/MailData/Envelope Index" )

* Legacy database in Android

* Firefox, Thunderbird

* Google Chrome, Edge

It is quick, simple, reliable and have enough performance for it's use case. Instead of using text files or develop own database formats.


This is the single worst project to make that comment.

tbh I don't think that really counts when it is a tool made by the sqlite developer.

sqlite is not a heavyweight database, it's a fopen() wrapper



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: