The only problem I have with SQL is that `SELECT` comes first instead of last. It prevents the development of good tooling.
also remember that sql is a query language not a programming language, so the main target are not programmers
also think of it this way, it might help, you start with that you really want
select firstname, lastname, hobby
so you start by saying you want a table (a relation, a relvar)
that have first name , last name etc ... this is what you want
then you tell me where to get it from from users
so the order is not bad , it like saying, get me a a drink from the box
you wont say, from the box get me a drinkselect first resembles more natural language, and is more declarative
from first, is more procedural
what i want first, then how --> declarative
how to find what i want, then what i really want --> procedural
vs
From Users Select Na...
select users.Na.. from ..
If your tooling doesn't work in the way you want with that I don't think there's reason to think it would if it were possible to write from users select Na..
either.