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. But in reality that question would be settled by other factors and contextual reasons rather than the arguments provided by the author.
For instance, analytics usecases favor SQL stores, as slicing and dicing is better done with row or column stores instead of document databases.
Also, Postgres is getting more popular for lot of usecases, so SQL is here to stay.
> 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.
For instance, analytics usecases favor SQL stores, as slicing and dicing is better done with row or column stores instead of document databases.
Also, Postgres is getting more popular for lot of usecases, so SQL is here to stay.