4 ms·
> On one axis, the license used is either Open Source (as defined by the Open Source Initiative (OSI), which I would summarize as coming with all freedoms neces
by phoe-krk 2y ago
> On one axis, the license used is either Open Source (as defined by the Open Source Initiative (OSI), which I would summarize as coming with all freedoms necessary to enable the permissionless innovation I mentioned earlier) or it’s not. On the other axis is the development model: it’s either developed as a commons, by a community working in open collaboration, or it’s developed (and ultimately owned) by a single entity.
Is SQLite "the new proprietary"? It seems to fit the description perfectly: very permissive license, very closed development process.
- ec109685 2y agoThat’s why the fork that is more open for contributions is gaining momentum: https://github.com/tursodatabase/libsql https://github.com/tursodatabase/libsql
- oefrha 2y agoYou mean the "single vendor" fork from Turso, the VC funded startup [1]? Thanks but no thanks, I'll stick with D. Richard Hipp. [1] https://turso.tech/investors https://turso.tech/investors