Re: SQL resists this workflow
> "note that the CAPS-lock is typically optional"
I haven't encountered any RDBMS that insisted on uppercase SQL statements. Most people I know who generate SQL simply use uppercase as a convention to help in distinguishing the SQL from column/table names.
Google's research labs are far from the only culprits coming up with strange and, frankly, questionable "innovations". The trend lately seems to be that "new and improved" replacement utilities are needed that take what has been a fairly easy to read and understand command syntax and transform it from a single line into something that requires multiple lines, braces, odd punctuation which, frankly, hides its purpose behind the new, obtuse syntax. It's hard to escape the feeling that all this seems to be getting done not because the current way of performing function X is broken in some way but, rather, just because it's "old".