1) Because it's a strawman argument.
2) Because the reply addresses a very small subset of apps, which 10gen specifically says is not recommended for use with MongoDB.
My point is simply that you gain productivity and Mongo tends to get a lot of hate on HN. My time is limited. For 90% of use cases, I am going Mongo.
Could you provide some examples? Scanning the list I see a couple that have a very periphery relation to financials, but the actual applications have very little financial applicability (and the implementations are trivial).
Though the person you responded to didn't actually say that `"anything that deals with money" has no use for MongoDB"', so you're setting up a strawman regardless.
But there's almost always some ACID requirement when you're dealing with accounting, e.g, crediting payment or billing fees.
I would use something that could handle transactional ACID processing in combination with MongoDB depending on the application.
I find that ironic.
Please have a little faith in other people, that if for any reason they're not using nosql it's a good one!