Computer Literacy is not the same thing as Computer Engineering or Software Development. I think in the analogy being tossed around with cars, what PP is talking about is more like getting a driver's license than becoming a mechanic.
Yes, exactly. Most of us, at least in the western world, use computers in our everyday lives. It's not just becoming inescapable, it already
has become inescapable. I'd actually venture to say that they're more prevalent than cars at this point, and if that's not the case yet, it very soon will be.
Most of those who own or otherwise use a car know how to drive one well enough not to cause frequent accidents. Most will have the sense to wear a seatbelt (and, in fact, it's the law in many places to wear one). Most of those who have a bank account understand the concept of an overdraft limit and know better than to cross it. They also know not to write their PIN right on the surface of their debit/credit cards. For some reason, the same does not apply to computer users.
This doesn't mean you should know every single thing about computers, or cars. It doesn't mean you should be an expert, a programmer, or anything like that. The sad reality we're facing right now is that many people think that some very basic computer-related tasks require said expertise. In the least serious of cases, this means that someone will pay me a disproportionate amount of money for half an hour of my time. In more serious cases, computer-illiterate people will go to www.bankofamerica.com.freepornsite.ru/moneystealingpage.asp and find themselves robbed blind.
Back in high school, I held a small talk about
phishing and tried to explain to people how a little bit of basic scrutiny can protect you from most attacks. While some people appreciated it, I ended up being heckled by a few people in the room, who felt it was appropriate to tell me that this kind of knowledge is reserved for nerds with no lives. I asked one of them if knowing how to avoid an obvious scam is really something that only boring nerds should know. His response? "No, but that's not what you're talking about. You're talking about boring programming stuff". Needless to say, I didn't mention programming throughout the talk at all.