> Anything else would be reinventing the same wheels SQLite has spent decades refining. Which is exactly the problem. They (I.e one dude?), and they alone have

> Anything else would be reinventing the same wheels SQLite has spent decades refining. Which is exactly the problem. They (I.e one dude?), and they alone have spent decades refining a single implementation. Before we go and lock the entirety of the worlds documents into what’s essentially a proprietary format specific to a single implementation of a single library written by a single dude… we should double check if that’s a good idea or not, and if we can, collectively, solve some of these issues without reimplementing the whole of SQLite. Because that’s complex. Perhaps more complex than it needs to be for most applications, which would benefit from the storage part more than the query part. And then we are back at the start of our discussion?