In fact, the 'MEAN stack' was coined by a MongoDB developer on his blog [1], a post which is a perfect example of the kind of marketing, anecdotes, messaging, and strategies that Mongo employed to stay relevant.
[1] http://blog.mongodb.org/post/49262866911/the-mean-stack-mong...
For example, Erlang/OTP brings a lot to the table. Being functional, it would protect you against certain types of errors leaving you free to solve more complex problems. You pay for it with run time performance. String operations are slow etc.
C++ is very fast and very sharp. Not easy to get everything right. (Some sort Greenspun's rule would apply here I think. Substitute Erlang for Common Lisp).
I am only saying that Mongo is not unreliable because C++ was selected; it's unreliable because of architectural choices and lack of care which may or may not have been intentional.
It fell behind in terms of perception while Mongo was chasing benchmarks early on but has seemingly continued to just keep chugging along with it's design decisions.
General community, "You sure about that? I mean...benchmarks."
Couch, "Yep...we're sure."
* few years later *
General community, "Have you seen CouchDB? This thing is really solid. Did you ever read that Hacker News thread about how terribly unreliable Mongo is?"