The last line here: "like any solution, SQL is facing increasing inadequacy in the support of the new requirements, modes of use and user productivity. It is ti

The last line here: "like any solution, SQL is facing increasing inadequacy in the support of the new requirements, modes of use and user productivity. It is time we do something about it." I agree, but I'm not sure the solution is to broadly replace SQL with something like EdgeQL. Graph Databases, BigTables, Document and Object Databases, Large scale key-value lookup tables... there are all kinds of solutions for problems that feel crammed into a SQL context. EdgeQL could be a great one in some scenarios - for example, when you need to do a lot of querying on arbitrary trees. Another solution is to go as far as the sweet spot of SQL can take you, and then switch over to a programming language (this is distinct from what is possible in SQL, the basis of many SQL programming interview questions)). I suspect SQL compares less favorably in a lot of scenarios that require a pure, single language solution. But may be we should be comparing SQL + Python with EdgeQL + Python (or even SQL + EdgeQL + Python).