We wanted the language to look as closely as possible to natural language so they could read it and understand it, like it was an English sentence
This may have advantages to appeal to non-technical people, but personally I consider it a fundamental issue. Cobol was also designed this way, but there is a reason we now use algebraic-like notation for programming and not Cobol.
It's relatively easy to write and understand a declaration like x1 = (-b + sqrt(b^2-4*a*c)) / 2*a, but if you try to express that as an English sentence you are going to be in pain, and anybody trying to read the result is going to be in a lot of pain.
I think it's very weird that a lot of SQL queries are built by concatenating strings that are afterwards parsed by the database engine. I feel like asking if the transmission should done by printing and scanning punch cards as well. We have so many ways to structure data in a logical way, it would make much more sense for queries to be defined, transmitted and read as a logically structured object rather than a string.
And yes, non-technical may be able to use SQL and would not understand structured data. They are also able to understand spreadsheets and not C++, but we still code in C++.