discrimination

We wrote earlier about the Paycheck Fairness Act, a bill of Orwellian deception that would result in employees unfairly receiving equal pay for unequal work.  It would force some employers to pay employees with dangerous or unpleasant jobs as little as employees with safe and pleasant jobs — as long as the different jobs have different gender breakdowns (that is, if one job is performed mostly by men, and the other job mostly by women — even if the employer does not discriminate in hiring at all, and eagerly hires qualified applicants of both sexes).

Now, it turns out that a lobbyist pushing this disturbing bill met with Senate Majority Leader Harry Reid on September 21, suggesting that the bill may be brought to the Senate floor in the next few days — and that there may be a major push to pass it.  (The Obama administration misguidedly supports the bill; the administration often gets the most basic facts wrong about discrimination and Supreme Court rulings dealing with sex discrimination.)

Labor economist Diana Furchtgott-Roth explains why this bill is a bad idea in The Washington Post.

Liberal Senators like Ben Cardin (D-Md.) and Dianne Feinstein (D-Calif.) are peddling fables about a Supreme Court ruling, Ledbetter v. Goodyear Tire & Rubber Co. (2007).

In its Ledbetter ruling, the Supreme Court said that employees who choose to sue under the federal discrimination law with the shortest deadline (Title VII) should generally sue within 180 days, at least where they could have discovered the discrimination in time to do so.  It rejected as untimely a discrimination claim by Lilly Ledbetter, who had known for years of the pay disparity she later sued over.

That’s a far cry from how Senator Cardin describes the case.  Today, in the Supreme Court confirmation hearings for Elena Kagan, Cardin made false claims, both about what the Supreme Court said in the Ledbetter case, and about plaintiff Lilly Ledbetter and her lawsuit.  In claims echoed by Senator Feinstein, Cardin alleged that:

“The Court said Mrs. Ledbetter had to file her case within 180 days after the beginning of the discrimination, and since she did not do that, her claim was barred by the statute of limitations. This defies logic. How can a person bring a claim when they don’t know they are being discriminated against? It makes no sense.”

The Supreme Court said no such thing, as National Review’s Ed Whelan, a lawyer, notes, pointing out that Ms. Ledbetter knew for years of the alleged discrimination before she chose to sue over it.  The claims made by Senator Cardin were long ago debunked by the Wall Street Journal’s James Taranto, legal scholars like David Copus, legal commentators like Stuart Taylor of the National Journal, and lawyers like Paul Mirengoff.

Plaintiff Lilly Ledbetter lost her pay discrimination case because she filed her complaint too late. The Court said that in most cases, employees should file an EEOC complaint within 180 days of their first discriminatory paycheck, if they want to sue under Title VII of the Civil Rights Act.

But the Court also specifically left open the possibility that employees could sue later simply because they didn’t know of the discrimination at the time — a situation it said did not apply to Ledbetter’s case (she testified in her deposition that she knew of the pay disparity in 1992, but only filed her complaint with the EEOC in 1998, around the time she retired). The Court pointedly noted that plaintiff could have pressed her claim instead under the Equal Pay Act, which has a longer deadline for suing. (Moreover, as lawyer Paul Mirengoff notes, the Supreme Court has long allowed hoodwinked employees to rely on equitable tolling, waiver, and estoppel to sue beyond the deadline, when employer deception keeps them from suing within 180 days, as it made clear in its Zipes decision.)

As Stuart Taylor, a legal commentator for the National Journal, has noted,

“Ledbetter admitted in her sworn deposition that ‘different people that I worked for along the way had always told me that my pay was extremely low’ compared to her peers. She testified specifically that a superior had told her in 1992 that her pay was lower than that of other area managers, and that she had learned the amount of the difference by 1994 or 1995. She added that she had told her supervisor in 1995 that ‘I needed to earn an increase in pay’ because ‘I wanted to get in line with where my peers were, because… at that time I knew definitely that they were all making a thousand [dollars] at least more per month than I was.’”

The Supreme Court did not create a rigid deadline that applies regardless of whether an employee could have discovered the discrimination.  Instead, it expressly left open the possibility that plaintiffs can wait to sue until after learning of discrimination, under the so-called “discovery rule.” It noted in footnote 10 of its opinion, “we have previously declined to address whether Title VII suits are amenable to a discovery rule. . . .Because Ledbetter does not argue that such a rule would change the outcome in her case, we have no occasion to address this issue.” In short, since Ledbetter didn’t even claim that a lack of knowledge had prevented her from suing in time, relaxing the deadline for her would have done her no good. (Moreover, if she had lacked knowledge as a result of being hoodwinked by her employer, she could have had the deadline extended under the Supreme Court’s longstanding doctrine of equitable tolling, which applies somewhat more narrowly than the discovery rule.)

After she lost her case, Ledbetter claimed to Congress that she had not learned of the discrimination until the end of her career — a claim parroted by gullible politicians and journalists before it was debunked.

But in Ledbetter’s deposition, she admitted she knew by 1992 – years earlier — that she was paid less than her male peers, notes David Copus in page 8 of the online version of his October 2008 law journal article “Pay Discrimination Claims After Ledbetter.”

Similarly, Washington lawyer Paul Mirengoff notes that “Ledbetter testified that she knew by 1992 that her pay was out of line with her peers. In 1995, she spoke to her supervisor about the problem, telling him that ‘I knew definitely that they were all making a thousand at least more per month than I was and that I would like to get in line.’ Yet Ledbetter waited until 1998 to file her EEOC complaint.”

Moreover, although the Supreme Court dismissed Ledbetter’s claim under Title VII, the discrimination law with the shortest deadline, it pointed out that the plaintiff could easily have pressed her claim instead under the Equal Pay Act, which has a much longer deadline for suing. As it noted, “Petitioner, having abandoned her claim under the Equal Pay Act, asks us to deviate from our prior decisions in order to permit her to assert her claim under Title VII.” She might have won her case had she simply appealed based on the Equal Pay Act, something she inexplicably failed to do.

Ladies’ night bar specials are illegal in Minnesota. They are unfair gender discrimination, according to the Minnesota Department of Human Rights.

Of course, few of the people actually affected by this blatant discrimination have a problem with it. Women save money on drinks. Men who buy women drinks save money. And by increasing the female-to-male ratio, ladies’ nights make men happy for other reasons.

If anything, enforcing the ladies’ night ban is a waste of state resources at a time when Minnesota is facing a severe budget crunch.

So why are regulators bothering? Blame lawyers. A separate case in New York has brought publicity to this divisive issue:

New York attorney Roy Den Hollander has for years made his living filing gender discrimination complaints for men, including himself.

Who cares? He does.

“[Men] have to pay more for the services [clubs] offer just because an accident of nature made them one sex or another?” he said. “That’s the basis of discrimination, and it shouldn’t be allowed.”

Or Mr. Hollander could simply choose to patronize bars that don’t do ladies’ nights. Other people seem to enjoy that particular form of gender discrimination. Let them.

Memorial Day is an opportunity to thank our troops, and open our eyes to the disgraceful way they are treated by divorce courts. The bias that divorce courts in my home state of Virginia often exhibit against males, people who start small businesses, and breadwinner spouses in general has been ably chronicled by Richard Crouch, a prominent family lawyer, in the Virginia state bar publication Family Law News.

But what ashames me most as a lawyer is how divorce courts routinely violate our soldiers’ rights under federal law. Crouch notes that Virginia courts ignore federal law by ordering members of the military to share their pensions with spouses who divorced them after even short marriages: “Something everybody learned early on is that a military wife had to have ten years of marriage to the service member overlapping ten years of military service to divide the pension. However, the Virginia Court of Appeals has adopted the rule that this statutory limitation in 10 U.S.C. 1408 limits only direct payment by the military of the former spouse’s half of the pension. Thus a service member can be required by a Virginia court to split his or her military retirement with the former spouse even if it was less than a ten year marriage. Cook v. Cook, 18 Va. App. 726, 446 SE2d 894 (1994).”

This contempt for the legal rights of divorced soldiers matters a lot, because soldiers have fairly high divorce rates, thanks to the stresses and strains of military life, such as unforeseen deployments overseas. Usually, it is the wife, not the husband, who initiates the divorce (two-thirds of divorces in America are initiated by the  wife, not the husband, although male spouses of female soldiers also initiate many divorces. Most divorces are no-fault divorces. By the way, I am not divorced).

Another way the state courts put soldiers at a disadvantage, and discourage them from serving their country, is to award their ex-spouses a share of their potential military pension starting at the earliest date they could possibly retire — even if they intend not to retire then but rather to keep on serving their country. That effectively forces them out of the military, depriving the armed forces of seasoned troops. This injustice is permitted, but not mandated, by federal law.

Lt. Col. Patricia Larrabee was effectively forced out of the military by “a court order directing that she pay her ex-husband a share of her retirement when she reaches 20 years of service in 2006, whether or not she retires.” “‘I can’t afford to write a check to my ex-husband every month out of my military pay,’ she told then-Defense Secretary Donald Rumsfeld. ‘By the way,’ Larrabee added, ‘he makes thousands and thousands of dollars more than I do.’”

Colleen M. Timpano, who served in the Navy, describes how she was royally ripped off by a state divorce court, which effectively “indentured” her “for life” to her “former husband,” who used drugs before and after his expulsion from the Navy, and “contributed absolutely nothing” to her career, even as she helped “finance his college education.” The court awarded her “ex-husband 30 percent of” her “retired pay for life, which will be paid to her “ex-husband and his third wife for the rest of his life.” Federal law did nothing to stop this.

State courts also jail returning reservists based on their inability to pay excessive child support levels that accumulated after they were called into service at pay levels far lower than what they received in civilian employment. The Bradley Amendment keeps their child support from being reduced retroactively when they return from the field of battle, even if they had no time to get their child support payments reduced before being suddenly called up and sent into battle. The Bradley Amendment has contributed to state courts jailing many hapless fathers, including “a veteran of the first Gulf War who was captured in Kuwait in 1990 and spent nearly five months as an Iraqi hostage before being arrested the night after his release for not paying child support while he was a hostage.” It also has resulted in “a Texas man wrongly accused in 1980 of murder” being billed “nearly $50,000 in child support that had not been paid while in prison” and a “Virginia man required to pay retroactive child support even though DNA tests proved that he could not have been the father.”

Even if a reservist manages to hire a lawyer to file a motion to reduce his child support payments to an affordable level while he is overseas, the child support agency often simply refuses to do so (sadly, this is not surprising given that child support agencies have a financial incentive to artificially inflate child support levels, since they receive federal funds based in part on how much child support they collect).

Nor can soldiers called off to battle just pay the child support in advance, if they have the money, to avoid complications of paying on a monthly basis while abroad. Virginia Delegate Jeff Frederick introduced a bill to allow child support to be paid in advance, but it was killed by the Virginia State Senate’s Courts of Justice committee. Dave Briggman of Prince William County, Virginia, was held in contempt for paying his child support early. When he could not afford to pay the penalty, he was then denied the ability to appeal the penalty based on his argument that he was unable to pay, based on the absurd Catch-22 ground that he had not put up an appeal bond in the amount of the penalty — something he by definition could not afford to do, precisely because he lacked the money to pay the penalty. Under the Virginia Court of Appeals’ decision in Mahoney v. Mahoney, if you want to appeal an excessive child support obligation or sanction based on the fact that it is beyond your means, you must first put up an appeal bond in the full amount you can’t afford.

Virginia has the weirdest case law on alimony in the entire southern United States. In Bristow v. Bristow (1980), the Virginia Supreme Court overturned a lower court’s refusal to award lifetime alimony to a wife who separated from her husband less than a year into their marriage, ruling that the trial judge could not deny alimony without making extensive findings, even after such a brief marriage, even though state law explicitly lists the duration of a marriage as a factor in whether to award alimony. (By contrast, in many states, like California, there is a judicial rule-of-thumb that alimony should not last longer in years than half the length of the marriage).

The Virginia Supreme Court’s “generosity” with other people’s money was selective and discriminatory. That same year, in Counts v. Counts (1980), the state supreme court barred a man from suing his ex-wife for deliberately maiming him, applying the now-defunct doctrine of “interspousal tort immunity,” even though Virginia circuit judges previously allowed ex-wives to sue their husbands for domestic violence under an “intentional tort” exception to that immunity. The state supreme court barred the ex-husband’s suit even though it had earlier (rightly) allowed an ex-wife’s estate to sue the ex-husband who murdered her in Korman v. Carpenter (1975). (In response to public outcry, the legislature eventually abolished marital tort immunity).

Divorce law is of enormous economic importance. Divorce cases outnumber any other category of civil case in state courts (nearly half of the docket of the Virginia Court of Appeals is made up of family-law cases), and redistribute far more money from any other category of case. And decisions by divorce courts on how to set alimony and child support payments can be potent disincentives to setting up a small business.

Virginia courts routinely do things that are economically inefficient and unfair, like allowing awards of permanent alimony even after very short marriages (Bristow v. Bristow, 1980), then allowing child support or alimony levels to be reset based on upward changes on the paying spouse’s income (Conway v. Conway, 1990), but not downward changes (Antonelli v. Antonelli, 1991), and allowing child and spousal support levels to be set based not on what the paying spouse actually makes (which would be an easy mechanical calculation that would not require any lawyer time or attorneys’ fees to compute), but rather based on higher, hypothetical (and sometimes arbitrary) estimates of what the paying spouse could make (”imputed income”), as in the cases of Cochran v. Cochran (1992), Antonelli v. Antonelli (1991), and Auman v. Auman (1995).

Setting support levels based on hypothetical rather than actual income results in lots of argument between opposing lawyers about what the hypothetical income should be, generating work for lawyers at the expense of the paying spouse. Similarly, allowing permanent alimony based on very short marriages results in lots of demands for such alimony by wives, and lots of arguments by their lawyers, even though such demands are often rejected anyway by the courts (see, e.g., Bruemmer v. Bruemmer).

Virginia’s divorce laws are an impediment to small business creation by divorced people, who comprise more than a million Virginia residents. As prominent family lawyer Richard Crouch once noted, Virginia courts employ a “heads-I-win, tails-you-lose” approach to people who try to start small businesses.

If you leave a steady salaried job in order to try to set up a small business, and it succeeds, increasing your income, you will have your child support payments increased over their prior levels (and perhaps your alimony payments as well). (Conway v. Conway, 1990.)

But if the business fails (as most small businesses do), resulting in your income falling below its prior levels, the courts will force you to pay alimony and child support as if you were still making the higher income you made at your prior job, rather than at the income you currently make (Antonelli v. Antonelli, 1991.)

As Crouch notes, “So much for encouraging small business. The wage-slave working stiff is shackled forever to salaried employment with big business, which he leaves at his peril.” Virginia gets a undeservedly generous rating from some business groups for how its courts treat businesses, but those ratings really only take into account how big business fares in tort lawsuits, and in reality, it’s Virginia’s fair-minded juries — not state judges — who make Virginia relatively “pro-business” in that respect.

I have often used gender-specific words such as “father” and “husband” to describe those who pay alimony and child support in my above discussion, even though state laws do not prevent judges from giving a father custody of the children or awarding support to the father. I do that because, in practice, it is usually the husband and father who pays them, and the law is not applied in a gender-neutral fashion, as Virginia attorney Richard Crouch observed in a 1992 article in Family Law News. (For example, the Virginia Court of Appeals denied alimony to a father even though his ex-wife made five times what he did, and he was the caregiver for the couple’s children, and instead ordered him to pay his ex-wife 40 percent of his meager disability pension, in Asgari v. Asgari [2000]. It is hard to imagine a similarly-situated ex-wife not receiving alimony for at least a few years.  For example, in Calvin v. Calvin [1999], the appeals court awarded a wife alimony despite describing her as adulterous, “vindictive and cruel”). As Crouch notes, in Virginia family law, “sex is the difference that makes a difference.”

Defenders of these rulings sometimes claim that they are needed to offset imaginary financial advantages enjoyed by non-custodial parents or men. Those claims are based on ignorance. Arizona State University’s Sanford Braver conducted his own study in the late 1980s, using better methodology, and found that ex-husbands do no better than ex-wives following a divorce, as he recounts in Divorced Dads (1998). Indeed, his study probably understates divorced husbands’ losses as a result of a divorce nationally, since it was conducted in Arizona, which has lower than average child-support collections (as the U.S. Supreme Court observed in Blessing v. Freestone (1998)) , and since it was conducted before increases in child support resulting from Congress’s passage of the 1988 Family Support Act, which prompted state legislatures to substantially increase state child support guidelines, awards, and enforcement.

Similarly, in 2000, a Virginia study (the JLARC study) erroneously claimed Virginia’s child support guidelines were too low only because it compared apples and oranges. It compared just one part of the state’s child support guidelines (the “basic” schedule, excluding statutory add-ons for health insurance and day care expenses) to ALL child-rearing costs, making the guidelines appear artificially low. It also treated as child-care expenses housing and other expenses shared by the custodial parent, for which the custodial parent could seek alimony — potentially resulting in the custodial parent getting paid twice for the same expenses, first in alimony, then in child support. If these errors had been remedied, the study would have found Virginia’s child support levels to be too high.

The same errors were behind a recent major increase in Maryland’s child support guidelines, which already exceeded the actual cost of raising children for most households.  (The legislation’s backers also falsely claimed that the guidelines needed a massive increase to adjust for inflation, even though the guidelines were largely self-adjusting for inflation).

Perhaps as a result of the unfounded belief that men generally suffer less than women after a divorce, states periodically rewrite their divorce laws to make life harder for breadwinner spouses. For example, Texas, which once forbade alimony as against public policy, now permits it under certain circumstances. North Carolina, which required a showing of fault by the breadwinner spouse to impose spousal support until the mid-1990s, no longer does. And as Richard Crouch notes, courts apply child and spousal support laws in a gender-biased fashion.

Separate votes” are expected “in the House and Senate later this week on legislation repealing the ‘Don’t ask, don’t tell’ restriction on gays serving openly in the military.”

I wrote earlier about the “Don’t Ask, Don’t Tell” (DADT) policy here.

Law Professor Dale Carpenter discusses the legislation to overturn DADT here.

I discuss some of the problems caused by DADT here; a commenter responds here. Cost-benefit analysis seems to support repeal of DADT.

The health care bills backed by President Obama will cost $2.3 trillion, not the $900 billion Obama claims, and will be a “budgetary disaster” that drives up the national debt, explains health care expert James C. Capretta.  The Obama administration managed to hide $1.4 trillion in costs generated by the health care reform bill though a series of budgetary “gimmicks” that the Congressional Budget Office (CBO) is required to treat as valid in scoring the bill’s enormous cost.

Although the CBO is low-balling the costs of ObamaCare, even it concedes that as a whole, “President Obama’s policies would add more than $9.7 trillion to the national debt over the next decade.”

ObamaCare spends money on frills like “cultural competency,” while cutting spending on crucial things like anesthesia.

Most Americans oppose the health care legislation backed by the president. It would reduce lifesaving medical innovation, raise taxes, drive up insurance premiums, break many campaign promises, and increase state budget deficits.  It  would jeopardize the quality of medical care, while imposing restrictions that failed when tried at the state level.  It ignores advice from doctors and federal experts, and lessons from countries with universal health care, about how to keep costs down.

Fact-checkers say Obama is lying about health care. Obama often contradicts himself. In the very same speech, Obama claimed that Medicare is “unsustainable” and “running out of money,” then contradicted himself by claiming that “Medicare is a government program that works really well,” making it a model for national health care.  The bill does nothing to curb massive waste and fraud in Medicare and Medicaid, even though it proposes to make massive cuts in Medicare (cuts so painful that most of them will never happen: year after year, Congress waives “the annual cut in fees paid by Medicare to physicians” mandated by an earlier law).

A CNN commentary noted that Obama’s plan would take away “5 freedoms,” contradicting Obama’s claim that the bill will leave you free to choose your doctor and keep your health care plan without government interference.

ObamaCare has also attracted criticism from groups like the Civil Rights Commission for containing both racial preferences and lower standards for treatment in predominantly-minority institutions, potentially harming both white applicants and minority patients.  This racial discrimination appears to violate court rulings like the Supreme Court’s Adarand decision, and the Rothe ruling by the Federal Circuit Court of Appeals.

A bill, SB 252, was just introduced in Maryland to increase child support obligations for households at most income levels–a massive increase of nearly 30 percent for a couple with one child making $3,400 a month!  Maryland residents, already burdened by recent state tax increases, now face additional burdens.

I don’t live in Maryland, and I’m not divorced, so I won’t be affected by the bill.  But as a lawyer who has studied most states’ child support guidelines, I find the economic ignorance behind the bill infuriating.

The bill is based on the bogus rationale that child support awards must go up, because inflation has increased child-rearing costs over the years.  But under Maryland’s existing child support guidelines, child support awards and obligations are based on income–the more you make, the more you pay!  So when incomes and prices rise due to inflation, so, too, do child support payments.  The guidelines thus contain a built-in inflation adjustment.

Yet some Maryland authorities apparently do not grasp basic economics, arguing that “today’s child support levels” are too low because they “are based on the economic realities of 1988, when a gallon of gas cost $1.08 and a first-class stamp was 22 cents.”

Wrong.  Child support levels are based on what payors earn now, not what they earned in 1988 – when incomes in dollars were much lower.  As Murray Steinberg, a former member of Virginia’s child-support review panel, noted, wages have gone up faster than inflation since 1988, meaning that child support levels have risen along with inflation, rather than being eroded by it.  (Steinberg cited publicly-available wage and inflation data from the Bureau of Labor Statistics proving this. See, e.g., Bureau of Labor Statistics, Employment Cost Index, Constant Dollar, June 1989=100 (April 29, 2005).) (Available at http://www.bls.gov/web/ecconst.pdf.  I used to work at the BLS producing federal labor cost and living cost data.)

The same false argument was unsuccessfully made in Virginia.  But its legislature wisely saw rejected it, and voted down a failed rewrite of Virginia’s guidelines based on this theory in 2006, rejecting a child support increase bill known as HB733.

Moreover, some child-rearing costs that rise the fastest with inflation – like “health insurance expenses” and “extraordinary medical expenses” – are awarded as statutory “add ons” on top of  the “basic child support” award, preventing their inflation from eroding the sufficiency of child support levels.  See Bureau of Labor Statistics, “Table 1A, Consumer Price Index for All Urban Consumers” (available at http://www.bls.gov/cpi/cpid04av.pdf) (medical inflation outstrips inflation in general). This offsets the fact that payments under the “basic child support obligation” schedule rise at a diminishing rate relative to income at the upper portions of the child support schedule.

Maryland’s guidelines are not inadequate.  They greatly exceed the true cost of raising children, and amount actually spent on raising children, for the vast majority of households making above $30,000 a year (and also for those households making less than $30,000 a year in which there are substantial court-ordered daycare payments awarded pursuant to Md. Code Section 12-204(g)).  Indeed, Maryland’s guidelines were historically above average for the nation, although that edge may have dissipated in recent years as some other states have jacked up their guidelines based on similar bogus inflation rationales.  (See, e.g., Ronald K. Henry, “Child Support At A Crossroads: When the Real World Intrudes Upon Academics and Advocates,” 33 Family Law Quarterly 235, 241 fn. 20 (1999) (lawyer notes that Maryland child support levels are above the national average, citing the example of a child support obligor with an income of $1000 per month).)

The bill would increase child support obligations so much that working-class fathers would end up paying more in child support than much wealthier families actually spend on their children.  I am a lawyer, and my wife is an accountant by occupation.  But we spend less on our daughter than the proposed child support guidelines would require many working-class non-custodial parents with much lower incomes to spend.  Households with a monthly income of $3400 have a higher “basic child support” obligation under the bill–not counting statutory add-ons–than I and my wife actually spend on our daughter, who has plenty of toys, games, food, and clothing.  (And that’s true even if our child-care costs are estimated at the maximum reasonable amount, such as by attributing to our daughter a per capita share of the amortized cost of our cars.)

(Ironically, the bill, while increasing child support payments at most income levels, would actually cut them for certain very low-income households, where child support payments actually come closest to matching child-rearing costs.  It increases the guidelines where they are most excessive now, and cuts them where they are least excessive.  “‘We’re reducing at the low end where it’s needed the most,‘ said Del. Benjamin F. Kramer.”  While I do not think that Maryland’s existing child support levels are too low even at the ”low end,” and would not object to a modest reduction there, it is odd to cut them only at the very low end while increasing child support awards everywhere else, even where existing awards grossly exceed the actual amounts actually spent on raising children by typical parents at that income level.)

State child support agencies like to boast of increased child support collections.  There are two ways for them to do that.  The easy way is to increase child support guidelines to jack up the payments imposed on law-abiding people who already pay their child support in full.  The hard way to do it is to make people who don’t pay what they owe now (many of whom are poor and have difficulty paying) finally pay up to support their children.  Maryland officials seem to have chosen the easy way out, at the expense of their citizens, and economic reality.

Previously, I wrote about a bill in Virginia, which will probably die, to sock divorced parents with discriminatory burdens.  Earlier, I discussed how divorce law increasingly harms veterans and small businesses, and the peculiar economics of divorce.

The D.C. government sometimes has more empathy for criminals than for their victims.   In December 2007, the D.C. Council voted to turn ex-cons into a protected class.

Now, it turns out that serial rapists are roaming free in the District of Columbia, since “Three thousand untested rape kits are sitting in a warehouse,” and D.C. has not even set up its own crime lab to nab rapists and other criminals using their DNA.

The D.C. Council hasn’t done anything about that.  But in December 2007, it voted to curtail employers’ and landlord’s freedom of association by banning job and housing discrimination against ex-cons, even though there’s a huge difference between discriminating based on someone’s skin color, and judging them based on the “content of their character.”  Even the Washington Post opposed the bill, noting that it “would undermine public safety.”

A Washington, D.C. law called the D.C. Human Rights Act also bans employers, including ideological and political organizations, from using political affiliation as a hiring criterion, or even adopting neutral policies that have an inadvertent “disparate impact” based on such criteria (with a completely different, and radically broader, definition of “disparate impact” than federal law).  Such mandates are of dubious constitutionality.  Contrary to the D.C. Council’s apparent belief, the government’s power to ban employers from engaging in reasonable job-related “discrimination” is not infinite.  See Nelson v. McClatchy Newspapers, 936 P.2d 1123 (Wash. 1997) (First Amendment barred application of state law holding newspaper liable for discharging reporter based on political activities).

Florida Attorney General Bill McCollum is questioning whether it is constitutional to force people to buy health insurance, as the health care bills backed by the Obama administration require.  This “individual mandate” is unprecedented and appears to exceed Congress’s power under the Commerce Clause of the Constitution.

As the Congressional Budget Office noted in 1994“,

A mandate requiring all individuals to purchase health insurance would be an unprecedented form of federal action. The government has never required people to buy any good or service as a condition of lawful residence in the United States. An individual mandate would have two features that, in combination, would make it unique. First, it would impose a duty on individuals as members of society. Second, it would require people to purchase a specific service that would be heavily regulated by the federal government.

As the news story about the attorney general’s concerns notes, in Supreme Court decisions issued in 1995 and 2000, “the high court said the commerce clause is limited to economic activities that substantially affect interstate trade in goods and services.”  (I was involved as an attorney in the latter of those two decisions, United States v. Morrison (2000)).

The individual mandate does not regulate activities, much less economic activities, but rather regulates based on inactivity, by penalizing those who decline to buy a product, health insurance (a product that young people generally do not need — as a young man, I did not go to the doctor or dentist, or purchase any drugs, for a 10-year period, and if I had become ill, my family could have easily paid my expenses).

That exceeds Congress’s powers under its Morrison and Lopez rulings, as I explained yesterday in a more extended analysis of the issue.  However, it is likely that at least four members of the current Supreme Court would vote to uphold the individual mandate, since the Morrison and Lopez decisions were 5-to-4 decisions.

Other aspects of the health care bills have also attracted legal criticism, such as their racial preferences and racial discrimination (it discriminates against white applicants in some provisions, and against minority patients in others; both forms of discrimination drew criticism from the Civil Rights Commission), and the manner in which they regulate insurance companies.

Regardless of whether the individual mandate is constitutional or not, it is certainly controversial — as are other aspects of the health care bills, which most Americans oppose.  As noted earlier, the bills would reduce life-saving medical innovation, raise many taxes, drive up insurance premiums and the deficit, break many campaign promises, and impose heavy burdens on state budgets.  They would also jeopardize the quality of medical care for many, while imposing restrictions that failed when tried at the state level, and ignoring advice from federal and academic experts, and lessons from countries with universal health care, about how to keep costs down.

Marginal Revolution’s Alex Tabarrok points to a proposed rule in California that would reclassify adult film actors as being subject to certain employment regulations. The unintended consequences are potentially fatal:

California’s anti-discrimination laws prohibit requiring an HIV test as a condition of employment; therefore the adult film industry’s current testing process, in which every performer is tested for HIV monthly, would be illegal. Nor would adult film producers be allowed to “discriminate” by refusing employment to HIV-positive performers. As a result, untested and HIV-positive performers would be able to work in the industry, raising the risks of HIV outbreaks–particularly since condom breakage or slippage can occur.

Sounds like regulators and activists need to think that one through a little more carefully.