Hacker News new | past | comments | ask | show | jobs | submit login

...and make sure your HR department is up to speed with the new rules. Hopefully this will make HR admin simpler, since everyone will now be subject to the same set of rules.



The Court's rulings today will have very little effect on the day-to-day of most HR groups, as they operate under state law. As I understand it (IANAL), today's ruling simply means that the feds must recognize any marriage solemnized in any state -- the feds are not allowed to have an exclusive definition of "marriage" anymore, so federal purposes like IRS income filings, etc., will be affected, but not the majority of tangible daily marital benefits, which are administered at the state level.

Unless you live in a state with full-fledged same-sex marriage, your HR dept. is still going to have to differentiate.


So why doesn't the Full Faith and Credit clause of the U.S. Constitution come into play here?

Section 2 of DOMA expressly released states from the requirement to recognize other states' gay marriages, but if it's struck down, "Full Faith and Credit shall be given in each State to the public Acts, Records, and judicial Proceedings of every other State."

So why wouldn't marriage apply? If it doesn't, I suspect this will be the target of new legal challenges.

[ETA: Apparently Section 2 of DOMA was not struck down. Sorry about that.]


The recent ruling was on the Constitutionality of Section 3 of DOMA, not Section 2. Section 2 is, as yet, still in force.

But, IIRC, recognition of out-of-state marriages without conditions has never been required by the Full Faith and Credit Clause -- this was actually one of the arguments against Section 2 of DOMA.


I was thinking of the California ruling specifically, since I live here and so do an awful lot of tech companies.

Although gay marriage was previously legal in California, between all the legal challenges and the passage of Proposition 8, it didn't become fully normalized for legal purposes (ie regulations that are indirectly affected by marriage laws). Now that process will resume.


Well, the California "ruling" was no ruling. The Supreme Court declined to rule on procedural grounds, so the lower court overruling of Proposition 8 stands.


Incorrect. The Supreme Court did not rule on the substantive issue, but did rule on the procedural question of whether Prop. 8 proponents had standing, deciding that they didn't. If they had declines to rule at all they would not have granted Certiorari.

In any case, implementation of the CA Supreme Court's decision could not go ahead until the USSC had issued its decision; now the state is free to promulgate new rules.


That's rather what I meant. From the NY Times article on the rulings (http://www.nytimes.com/2013/06/27/us/politics/supreme-court-...):

The case concerning California’s ban on same-sex marriage, Proposition 8, was decided on technical grounds, with the majority saying that it was not properly before the court. Because officials in California had declined to appeal a trial court’s decision against them and because the proponents of Proposition 8 were not entitled to step into the state’s shoes to appeal the decision, the court said, it was powerless to issue a decision. That left in place a trial court victory for two same-sex couples who had sought to marry.

I'm belaboring the point to make clear that the Supreme Court did not rule on Proposition 8 itself.


> In any case, implementation of the CA Supreme Court's decision could not go ahead until the USSC had issued its decision

The actual decision that can now be implemented is a decision of the US District Court for the Northern District of California (a federal trial court that struck down Prop 8 as a violation of the federal Constitution), not the California Supreme Court (the state appellate court who upheld the Proposition as a valid Constitutional amendment and not an improperly-passed Constitutional revision under the State Constitution.)


You're right, thanks for the correction. It's been through so many rounds at this point I get them mixed up at times.


How long until the feds step in and make it mandatory for all states to recognize same-sex marriage?


If today's ruling is any indication, never. It would be unconstitutional.


Does anyone expect that to hold? It seems obvious that they just needed something that seemed vaguely like a legal basis to justify the decision. It's at least not as egregious as Griswald, but I definitely think they're reaching with the "feds can't have a custom marital definition". If they're going to say it's illegal for the federal government to define marriage because marriage is a state-level thing, they may as well also say it's illegal for the federal government to consider marital status altogether.


Well and beyond that, they're setting a strong precedent for future state's rights cases. I happen to be in favor of that by the way, despite ambivalence towards this particular issue.


Well, I'd expect it to before the Supreme Court on the merits fairly quickly, now that the Nevada and Hawaii the Ninth Circuit cases that were on hold pending the Hollingsworth and Windsor decisions can move forward.


Probably not too long on the macro scale, but I'd still say there's several years to go before it's universal applied.


When Democrats will regain the House and a super majority in the Senate.


What you want to happen will happen through the judicial branch, and the composition of the House and Senate will be irrelevant. I'm guessing three to five years.


> What you want to happen will happen through the judicial branch, and the composition of the House and Senate will be irrelevant.

Last I checked, the composition of the Senate had a pretty big impact on who gets into the judicial branch of the US government.


Sure - but the majority for the decision is already there.


My impression -- and its no more than that -- is that the current court splits 5-4 against marriage equality as a right.


Not as simple as that.

Though federal benefits cannot be denied to married same-sex couples, state benefits can be if same-sex marriage isn't recognised in the state.

This still presents some headaches for some people and even the most well-meaning of employers.

For instance, imagine if you have a same-sex couple living in a state that doesn't recognise SSM (say, Wyoming) but who married in a state that does (Washington State). One of the two is working for a company just across the border in Washington State, but the other doesn't. Now imagine that the state provides health coverage while a person is unemployed, but it doesn't cover people whose partner's employer provides healthcare. Is the employed partner's health insurance liable for treating his unemployed partner or is the state liable to provide coverage?

What about when a couple is travelling? Is a gay partner covered by their partner's health insurance when visiting a state that doesn't recognise SSM? What about states that have civil unions rather than full SSM?

In Britain, it has been discussed a fair bit this week that even though since 2004 we've had civil partnerships which are supposedly "marriage in all but name", gay people in civil partnerships are still not getting fair treatment regarding pensions. As an openly gay man who might as some point want to get married, I've followed the news and discussions around the legislation on same-sex marriage in Britain fairly closely and I still don't know what the situation with pensions is, but apparently it's still broken.

I think things will be in a bureaucratic mess for a while. It'd probably be easier if it could be legalised across the whole country in one fell swoop... but that might just be wishful thinking on my part.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: