> So I guess the author is trying to help a decision maker to make a decision when faced with a question of whether to use SQL or not. That's not my impression

> So I guess the author is trying to help a decision maker to make a decision when faced with a question of whether to use SQL or not. That's not my impression. A decision maker today should typically make the decision to use SQL. I'm pretty sure the author would agree with that. I think the target audience is language designers and tool builders. The author is urging people to envision and build new better interfaces to interact with relational data.