I don't shoot to make $$$, but seems to me Jonathan's concern is very legit. While I don't like to hear camera brand bashing either, I don't see why every Nikon owner is cutting Nikon quite so much slack in stuff like this. If lots of your main clients or prospective employers (in whatever field you're in) is showing strong preferences for something you can't offer, shouldn't you be a little concerned and try to address them as best you can?
For instance, in my field, people can choose to stick w/ Cobol(!) or Fortran or even C instead of adding C++ and/or Java or something else newer to their knowledge/expertise or choose between Unix/Java and Microsoft/.NET or whatever else, but you better believe their choices have consequences. In very many cases, you can certainly get the job done w/ a variety of approaches and skill sets, but the client or prospective employer isn't often flexible about it for many reasons that are beyond your own control.
And if Sun, et al wants to keep competing against Microsoft/.NET as development platform of choice, they better do some hard work selling to the clients who will employ the developers for their projects, etc.
Do you not think it costs developers something to have to switch expertise in platforms? It's not always direct monetary cost, but there are costs nonetheless.
All that is really very similar to this particular Nikon vs Canon thing as far as I can tell. And honestly, I want Nikon to do well -- and I'm not hung up on needing them to churn out products like Canon does -- but sometimes, it does seem like they might need a reality check.
_Man_