Think about who the higher ups at Mozilla are. Brendan Eich is CTO, for instance, and you can see exactly what he thinks about supporting NaCl right now if you look at his recent posts :)

We might prioritize things based on input from Google (we tend to listen to things Google's web properties have to say since they run some of the biggest websites on the planet). This is usually a collaboration between the technical folks at both organizations to drive things that are best for the web.

We're not going to implement things that we think are bad for the web just because Google says so. You can look around to see what Brendan Eich (CTO of Mozilla, a higher up by any definition) has to say about Dart and NaCl. Google's money doesn't buy our cooperation on these kinds of issues (and it's worth noting that we work with plenty of people who aren't paying us money, such as Facebook, the same way that we work with Google).

That notion could not be more wrong.

You mean just like happened with WebSQL and Google's attempts to push back on the Do Not Track header?

I suggest you read any of the w3c/whatwg mailing lists where Mozilla and Google folk discuss issues.

I don't think you can accuse Mozilla of caving in to Google demands at all :)

Which, while annoying for you if you happen to want to push one of those things, is a fantastic thing for the Web. We all simply want to build a better web - and out of the disagreements, we get clarity how to do that.