In case anyone is wondering he is talking about EdgeDB (https://www.edgedb.com/)
I have absolutely nothing against EdgeDB or its creators. As far as I can tell, it's a great product.
That's a very commonly known technique where you purposefully take only the overly simplified points that you want to counter so that's easy to build arguments or say things like "What can your language offer besides being created in the 2020s?". This is not to say the author or majority of the readers would find what EdgeQL offers, other than being created in the 2020s, valuable but at least you wouldn't be fighting a straw man.
Other responses note some (to me) esoteric enterprise use-cases for which SQL may not sufficiently describe exotic data vistas. Sure.
But most of the "shaming" one encounters seems to be about advertising some sort of magic wand product more than pointing out a substantial woe in a system that has been prominent for a half century.
EdgeQL:
select Child {name}
filter .<child[is Parent].name = 'Uma Thurman';
select child.name
from child
join parent_child_rel using (child_id)
join parent using (parent_id)
where parent.name = 'Uma Thurman';