News for hackers. Stuff that matters.
Re:Why SQLite succeeded as a database (2016) by nindalf on Thursday January 05, 2023 @10:30AM (#34261022)
> open source but not open contributions

I never understood this. Does it mean other open source projects are "open contributions" and anyone can just go ahead and commit to master? No. Literally every project requires you to have a discussion with the maintainer(s) before your contribution can be merged in. In larger projects, it requires going through a change process.

Re:Why SQLite succeeded as a database (2016) by Tomte on Thursday January 05, 2023 @10:37AM (#34261151)
> Literally every project requires you to have a discussion with the maintainer(s) before your contribution can be merged in.

But they can be merged in.

SQLite clearly says "not interested in your code". At all.

It's not like they are unfriendly. They will happily discuss things in detail with you, but you can publish your own extension. SQLite proper is developed by Mr. Hipps and his friends/employees.

A very sensible model, if you ask me.

Re:Why SQLite succeeded as a database (2016) by metaltyphoon on Thursday January 05, 2023 @12:25PM (#34263227)
What amazes me is how people are insensitive about other choices.
Re:Why SQLite succeeded as a database (2016) by mort96 on Thursday January 05, 2023 @02:40PM (#34265372)
With almost any other project, I can take the source code, make some change, and then propose that the upstream project incorporates my change. If the upstream project thinks my code is good, they will incorporate it as-is.

With SQLite, that's just not a process. There is no process whereby code written by anyone other than the SQLite maintainers enters the git repository.