- sqlite can't do concurrent writes, which is a performance bottleneck for certain workflows
- sqlite is synchronous, which isn't ideal in applications that are async
- while sqlite itself is open source, the test suite is proprietary, which means forking it and adding your own features or bug fixes isn't really practical. Of course, that is also a significant barrier to turso having sqlite compatibility.
Does turso really solve those problems? IDK. Does it introduce new problems? Almost certainly. But those are real problems that people have.
alt Hacker News
I think the problems with sqlite:
- sqlite can't do concurrent writes, which is a performance bottleneck for certain workflows
- sqlite is synchronous, which isn't ideal in applications that are async
- while sqlite itself is open source, the test suite is proprietary, which means forking it and adding your own features or bug fixes isn't really practical. Of course, that is also a significant barrier to turso having sqlite compatibility.
Does turso really solve those problems? IDK. Does it introduce new problems? Almost certainly. But those are real problems that people have.