Except it is increasingly not fine. Even your response above is explicitly assuming the person who would say this doesn't like programming because they have no interest in doing personal coding after their professional coding is done.
As someone who really likes his job, derives significant satisfaction from it, and is constantly looking to get into more interesting work, yet doesn't feel like doing more than ~50 hours of this a week and has other interests (including creating run-on sentences apparently :P) that I wish to pursue, this false dichotomy between "Only cares about a paycheck" and "Passionate programmer who can't resist writing and publishing code" is damaging and demoralizing.
TurboHaskal explicitly said that those of us who work on open source projects in our free time must be "faking passion...to appeal to recruiters." That implies a worldview where nobody does programming for fun and that open source contributors are just pursuing additional strategies for making money. It's a depressing thought and absolutely is antithetical to the notion of liking programming.
It's fine if you have other interests and only want to program for 50 hours a week. But don't accuse me of "faking passion" because I program for 80 hours a week.
Nowhere does TurboHaskal accuse people who work on open source projects of "faking passion". He said he should not be forced to "fake passion" by writing open source code just to have open source code, the implication being that if one were really passionate about software development one would be compelled to do so. It isn't a statement about people who actually want to work on open source projects outside their day jobs.
Both your and the grandparent comments have an imperfect analogy. No one gets paid for doing professional archery as a daily wage-earning job in the modern world.
I would say our position is more akin to professional car mechanic setting up shop on weekends and offering something like "I'll fix your car for free and teach you how to do it, but no guarantees!" Would professional mechanics accuse him of devaluing their industry? Probably. Could he say "I like to fix cars in my spare time, and I'm doing what I love. Buzz off!" Sure.
Here's the thing though -- auto mechanics, they have unions and certification, and therefore are probably more aware about downward pressure on wages and such. Which is why you won't find many qualified hobbyist auto mechanics on the weekend like I described. (On the flip side, their flexibility is far more limited than programmers'. So I'' still take the programmer job.)
Nobody is saying you should work for others for free.
Tons of car mechanics do in fact spend their weekends tinkering on cars for fun. Some of them restore old cars, others work on custom modifications. It's a whole part of car culture. Hobbyist auto mechanics absolutely are a thing.
Of course, nobody thinks they're devaluing the work of other mechanics by scratching their own itch on weekends. Likewise, when I work on my own personal projects it doesn't "destroy the industry." I'm not doing bespoke work on other people's projects for free, I'm building stuff I personally find fulfilling.
Tons of car mechanics fix up old cars for themselves on the weekend. The difference is that when they fix their car, they don't fix that car for anybody else with the same problem, which is a serious limit to the mechanic metaphor.
If you don't have time to code outside work, that's fine. Just don't accuse the rest of us of faking it.