I don't think we have a difference of opinion on what Google does, just on what chromatic was trying to communicate. I think he was implying that Google is a bit pretentious in their interviewing when it seemed to amount to a regular sysadmin job from his perspective. It appears what you took from it is an assertion that Google is somehow stealing data and locking it up, and that's a bad thing? I'm still not exactly sure what you took from his text on that subject, your reply seems to be justification of your position, not clarification on what exactly you interpreted and found worth rebutting.
That said, my take on his reply to your original comment is that he really interpreted it as a shit job. I'm not sure if that's just the work at the level they decided he fit at, or is par for the course, but I can see how someone who identified as a programmer may be put off by an interview where they ask "Is it a problem for you to be maintaining code but not writing it?"
I think he was implying that Google is a bit pretentious in their interviewing when it seemed to amount to a regular sysadmin job from his perspective.
This, and my CV says system administrator exactly once, and that ended in 2000. Everything since then has been not system administration. To be pigeonholed into system administration because the mighty algorithm had decreed that the intersection of "Perl" and "system administration" on a CV meant "system administration" did not sit well with me.
That said, my take on his reply to your original comment is that he really interpreted it as a shit job. I'm not sure if that's just the work at the level they decided he fit at, or is par for the course, but I can see how someone who identified as a programmer may be put off by an interview where they ask "Is it a problem for you to be maintaining code but not writing it?"