Monday, May 24, 2004

“Vasectomy Prevents Abortion”

I had just finished my dinner at Osteria del Figo, which it turns out is an excellent Italian restaurant (good food, low prices), and on the way out happened to spot this bumper sticker on a moped outside. Something clicked in my head, and I suddenly realized that English usage has made it so there is no semantic difference between the language that we use to describe vasectomy and abortion—or between abortion and any other non-abortion child prevention tactics—making it more difficult to dicuss abortion and similar procedures in isolation from preconception pregnancy prevention.

Essentially, the term “birth control” is used to apply to all forms of pregnancy prevention, but I submit that this is not only incorrect, but making it more difficult for pro-life advocates to frame the debate. For many (though certainly not all) pro-life people, there is a fundamental difference between using “the pill,” condoms, or abstinence, which should really be called “conception control,” and the methods of abortion, et al., which are truly “birth control” since they directly control whether a birth occurs.

Unfortunately, the language didn’t evolve that way, and attempts to narrow the definitions of words, even to a more correct definition, are notoriously prone to failure (see “hacker”). This means that the language does not itself imply the bright line that is conception is relevant; instead we (as a nation) have decided that the line is fuzzy, and that it is nowhere near the conception line, the one definite point of reference.

Is this Newspeak? No, for one, I don’t think that this was an intentional abuse of language with the intent of changing the way that we think about things. But humans categorize and we name. Without it’s own name, it’s a lot harder to talk about.

I expect the worst…

Anyone coming here from Mr. Tompkins’ site, I’d just like to say “hi.” Umm, yeah, you’re also wondering about why my page renders so horribly. It’s because you’re using IE and I’m explicitly incompatible with that browser.

Now you’re wondering, “where does he get off trying to fix some other guy’s CSS, when his own is broken on the most popular browser on the planet?” My answer is that I thought it would be an interesting exercise, and it was. And though he isn’t going to use my patched CSS files (which were, incidentally, broken on IE, though I don’t know why this time) I appreceate the link and the discussion.

And yes, this site’s run on Blogger. So sue me. Limitations of my host. (You’d think Georgia Tech would be up to date on this stuff, but if you go to the root on this server, you’ll see the last message of the day was posted four years ago. I’d say no one has touched this server’s backend in years.)

  • Powered by WordPress, state-of-the-art semantic personal publishing platform.
  • Get Firefox