I actually tend to believe many developers realize that data in a relation DB is not the only way to go about things. Having spent my entire adult life in a SQL bubble it's refreshing to have all these alternative tools now that can do more for me as a collective whole. But of course blindly doing anything without a reason is a bad idea.
For me, Mongo blows any RDMS out of the water with regards to prototyping and getting an idea into a working solution. That alone is why I use it exclusively for new projects - under the guise that if any of the projects ever become successful I'll have to split things out into their respective buckets. So far, I haven't been fortunate enough to have these problems.
Can you give a concrete example where MongoDB blew an RDBMS out of the water in regards to prototyping? I find that database schemas don't really get in the way until a project matures, and then it becomes a road block both in a legacy manner and that making changes puts strain on the database infrastructure.
I can't remember the last time a schema I made in week 1 was similar to the schema in week 4. That alone is why I made that statement. Modifying schemes requires modifying code all over the place that relies on it. The majority of the time, with Mongo, I can ignore those changes and only code for what I added.
That is my experience. Perhaps you have the patience and foresight to plan out your schema well before coding.
For me, Mongo blows any RDMS out of the water with regards to prototyping and getting an idea into a working solution. That alone is why I use it exclusively for new projects - under the guise that if any of the projects ever become successful I'll have to split things out into their respective buckets. So far, I haven't been fortunate enough to have these problems.