Thank you for sharing the story of EdgeDB! I'm probably one of the early adopters of it. Honestly I don't want to write SQL never ever ever again after using E

Thank you for sharing the story of EdgeDB! I'm probably one of the early adopters of it. Honestly I don't want to write SQL never ever ever again after using EdgeQL. Currently I'm migrating some of my projects to EdgeDB and already have one in production (it's low importance project in a beta-stage, so I can afford some risks). I also wrote my own scaffold generator for the stack I'm using (EdgeDB+Go+gRPC+Flutter), which generates .esdl and Go database-related files for me. 7+ months later I'm really impressed with user/dev-friendliness of the tooling. It's mostly a "just work" experience, error messages are surprisingly clear (and, thanks God, no python stacktraces on each error or wrong input). Speaking of which, I would still be happier if EdgeDB was written in Go (seems like the best fit for this niche), but I get that authors were more proficient in Python, and it works pretty great so far. Some nitpicks that I have (all minor ones): - in edgedb console shell if you hit Enter key it doesn't execute the query, but breaks the line. So there is an extra step to move cursor back to the end of the query before executing it (which is frustrating when you have to go to the middle of the query, change it and execute). - I'm still not happy with how Optional types are implemented in Go library – end result, while being 100% correct and explicit, is overly verbose. Not a big deal when using code generator, but I feel like library API would benefit from simplifying it (I wrote some comments on github some months ago). Anyhow, EdgeDB is a game changer and I'm looking forward for the stable 1.0 release!