well its trade off , its easier to read, maybe a bit harder to write
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 drink
select 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
If I start deciding on my with the table, my query editor can tell me what I can select. I've never seen a query editor that looks at the select table and suggests tables based on that.
Anyone not using ORM, will eventually build his own ORM (or at least query builder). I think the argument is not about "not using ORM", but more about "not using ORM made by someone else".
I've been programming only for 8 years almost every single day. I've never do professional programming before, except teaching how to program. Well, I am actually a teacher. I'm looking for experience to do programming professionally.
