Earlier quoted context omitted.
Right, but conceptually the way you interact with it is the same. I'm not trying to belittle what you've done. I'm in fact very excited about it. And EdgeDB is very needed because it's just an Apple library currently. Conceptually, my impression is that EdgeDb is relational tables (highly-typed) queried, combined, and modeled as nodes in a graph/tree. Is that conceptually correct? I don't, but I would like to if I co…
That's correct! Though that's true for most ORMs as well, and we try not to get lumped into the ORM bucket...too much bad blood. I've dabbled with CoreData myself and it's a phenomenal API. Apple comes up with a lot of great stuff. In fact, given how much server-side Swift there is these days, we'll have to look into building a Swift client library at some point.
I hope EdgeDB is immediately recognized for the value it will bring to developer productivity everywhere!
Now we just need an SQLite version of EdgeQL (perhaps EQLite) for local data and it can completely replace SQL in my life.