Tom, it really depends upon the requirements. I like using MongoDB, but I get far more calls for PostgreSQL.

I often prototype new applications and databases using MongoDB because I can rapidly iterate logical database structure. Once the data model firms up I can create a relational schema and switch to PostgreSQL.

It helps that I always access persistent storage through a REST API that sits on top of data connectors that are database technology agnostic.

Much as I like document databases like MongoDB, I cannot agree with you that you can do anything with noSQL that you can with SQL. There is a universe of difference, both in functionality and performance, depending upon what you need to do

Each has its place and each has its cost. I just try to build my applications to be flexible, so that they can work with either. Then it doesn't cost me or my customers too much if we have to change our minds.