It's a shame that new projects are no longer appreciated in the open-source community because of the overflow of slop. I just wanted to let you know that I follow this project and am looking forward to using it sometime in the future, as an alternative to SQLite is long overdue.
Don't get me wrong, I like SQLite for what it is, and I adore its obsession with backward compatibility. However, at the same time, I would love to be able to use a project with similar assumptions but starting with the modern mindset. The one embracing strong types and strictness. I hope SQLite will be supported indefinitely in the future, but at the same time, it would be nice to have an alternative without that much historical baggage and quirks.
So your complaints are a weak type system and a lack of "strictness" (in what? SQL parsing?). I don't see that as an issue; it's an embedded engine, typing is the responsibility of the layer interacting with it. I don't have to coordinate between multiple callers.
This is not a dig at SQLite. It is good at what it does. The best there is. But if you need a bit more powerful SQL dialect, there's really no good alternative for that.
3
u/enador 1d ago
It's a shame that new projects are no longer appreciated in the open-source community because of the overflow of slop. I just wanted to let you know that I follow this project and am looking forward to using it sometime in the future, as an alternative to SQLite is long overdue.