Colin (EdgeDB employee) here. We're happy to announce the first release candidate of EdgeDB 1.0! We'll be releasing RC2 in a couple weeks, followed by a stable release shortly thereafter.<p>Quick TLDR of what we're trying to build: we think some of the design choices in SQL are holding back relational DBs from providing the best possible developer experience. Namely: non-composable syntax, OOP-incompatible (and ultimately unnecessary) concepts like foreign keys and JOINs, and the lack of first-party migrations. The lack of these things is what drives developers to ORMs and other non-optimal abstractions. See a previous HN discussion of EdgeDB and our query language EdgeQL here [0].<p>We’ve received a lot of great feedback on HN over the years. Feel free to check out some recent threads about the design of EdgeQL[1] and the limitations of SQL[2].<p>[0] <a href="https://www.edgedb.com/blog/we-can-do-better-than-sql" rel="nofollow">https://www.edgedb.com/blog/we-can-do-better-than-sql</a><p>[1] <a href="https://news.ycombinator.com/item?id=27793398" rel="nofollow">https://news.ycombinator.com/item?id=27793398</a><p>[2] <a href="https://news.ycombinator.com/item?id=24106608" rel="nofollow">https://news.ycombinator.com/item?id=24106608</a>