Showing posts with label relationships. Show all posts
Showing posts with label relationships. Show all posts

Monday, March 12, 2012

Feminist Relatioships: Put A Ring On Him


Especially in the age of Facebook, nothing marks an engagement like a closeup of a big, shiny ring on a girl’s finger.  Men propose to women, they give them shiny jewelry, and women go into “bridezilla” mode.  Thus is modern courtship.  Righ?  That’s how it’s supposed to be?

There’s the stereotype that women are the ones that chase down marriage.  They practically beg for engagement rings because they want to get married and have lots of babies.  And the men hold the elusive ring—it is to be doled out a their discretion whenever they want to.  And women are supposed to sit around and wait to be proposed to.  Because it is no ladylike or proper for us to be the aggressors, especially since we want marriage and babies from day one of any relationship.  Right?

What if it became socially acceptable for women to propose to their male partner?  What if we could finally, without scrutiny, get down on one knee and whip out a ring for our boyfriends?  We could take over control of when it is acceptable to enter into an engagement, a control that has been male-dominated for a very long time.  No to say hat couples should no discuss how prepared they are for marriage before they enter into an engagement, but it would be nice to get to initiate it, right?

And what about how unfair it is that we get to carry around this little platinum dog leash on our left hand while guys can walk around with no physical indication whatsoever that they are engaged?  All things being equal, isn’t it only fair that either both of us have o wear a ring or neither of us do?

Thus enters the popularity of “mangagement rings”.  They’re engagement rings for men.  That way, both of you get to have a ring!  You’re both officially taken!  Awesome!

Of course, there’s a style difference between engagement rings for men and women.  Sparkly diamonds are jus too feminine for the manly men, they need plain bands.  And women would be so bored without something shiny on their fingers to distract them and announce to the world that their significant other was willing to spend a small fortune on a rock.  Personally, I prefer non-diamond engagement rings.  Beyond that sticky blood diamonds thing, I think that the appearance of an engagement ring—be it for a man or woman—should show that person’s individuality and style.  Heck, if you would rather have an engagement toe ring, more power to you!

I hope that mangagement ring trend will really pick up here in America.  I think it’s a fantastic way to equal out the power dynamic, and make men feel like their engagement and wedding are about them and not just their female counterparts.  It would be more fun for everyone!  

If you're interested in reading up on the history of engagement rings, this is a very interesting article from Slate, and this is a fascinating, condensed timeline that shows some interesting parallels between the uses of rings or wedding jewelry and a man taking ownership of a woman.  Enjoy!

Sunday, March 4, 2012

Feminist Relationships: White Wedding?

In this week's installment of Feminist Relationships I would like to talk about un-traditionalizing the traditions of weddings.  There's nothing wrong with having a big, fun wedding and being a feminist, no conflict there.  But there are a few things about traditional wedding ceremonies (and receptions) that could use some Girl Power.

Let's talk pretty dresses for a second.  The wedding industry makes millions of dollars a year off of those big, poofy white confections that brides glow in as they walk down the aisle.  The traditional gowns are white or off-white (a choice that's becoming increasingly popular) and come in a variety of styles, though they're most commonly a little on the lacy and taffeta-y side.  Nothing wrong wit that, if that's what you feel most beautiful and bride-like in.  But the white wedding dress does carry some pretty hefty baggage, and not just in that giant bustle.  White wedding dresses imply virginity, which is why the off-white is becoming more and more common for second marriages.  It's a way to prove that the bride hasn't been defouled in the bedroom as she's being delivered to her new husband.  Seeing as premarital sex isn't exactly uncommon these days (nor has it ever been, for that matter) these pretty poofy packages are often concealing a lie.  I don't need to announce my sexual status to the world anyway--my husband sure as hell won't be hanging any bloodstained bedsheets in the window after our wedding night--so I don't feel the need to broadcast my virginity with my wedding dress.

There's nothing wrong with breaking with tradition and wearing something colorful, like blue or purple, on your wedding day.  For me, it comes down to this: if your wedding day is a big enough deal that you want to wear something spectacular, wear your absolute favorite thing regardless of style or color.  If that's white, awesome for you.  If that's something else, go for it!  It's your day, after all.

Then there's the person that's going to be delivering that pretty package.  I use that kind of objectifying language intentionally--historically, the bride was pretty much transferred as property from her father to her new husband.  That's why fathers walk their daughters down the aisle.  It's called "giving the bride away" for a reason.  I don't know about you, but if I'm getting married it's going to be my choice and therefore I'm giving myself away.  No one has the right to do that for you.  If it's important to you to have your father, or mother, or some other important figure in your life take part in the ceremony in that way, that's totally up to you.  But for me?  I'll be walking down that aisle solo.

Then there's that whole "man and wife" thing.  This is less common these days than it used to be, but I can't understand why it couldn't be "man and woman" or "husband and wife".  But since us ladies used to be considered property, I guess it made sense for the times.

Lastly, that bouquet toss.  There's a scene in a crappy romantic comedy from the late '90s (pretty broad genre there) that had an interesting metaphor about the bouquet toss.  Girlfriend catches the bouquet, her boyfriend gets roped into marriage.  The girl who catches the bouquet is supposed to be the next to get married, and us ladies are supposed to fight tooth and nail for a bunch of half-dead lilies so we can be next to get a ring on our finger.  I don't feel the need to perpetuate that kind of stereotype.  Plus, flowers are expensive and if I paid for them I'd want to hang onto that bouquet, thanks very much.

Sure, you can find half a dozen other things wrong with the traditions of marriage and weddings if you dig deeper.  There are plenty of them.  But, in the end, weddings are supposed to be fun.  They're a chance to eat, get hammered, get free cake and dance like an idiot.  Everything else is up to you.  Though, ladies, your fiances should really have some say in this, too--we aren't the only ones who like weddings, and that sitcom trope is pretty tired by now.  It's really about who you are and what you want for your wedding, whether it's a big deal or a quiet thing between you and your soon-to-be spouse.

I'm going to write about engagement rings next week because of this new trend in mangagement rings (that piece is just a teensy bit problematic, so you know).  It's an interesting topic to delve into, so I hope I'll see you back this time next Sunday.

Sunday, February 26, 2012

Feminist Relationships: The Last Name Conundrum

This is the first of what I hope to be many installments of a weekly Feminist Relationships series.  This week's topic has been on my mind for the past couple of days since Jezebel linked to this study about how people in the Midwest are more likely than they were 20 years ago to judge a woman for keeping her last name when she gets married.  Apparently, ladies, this means that we aren't as "committed to our husbands" as name-changers if we choose to stick with the name we were born with.  Which I think is pretty unfair.

I have my mother's last name, which is not a common occurrence.  Sure, it was just because she got to the birth certificate before my father and they were unmarried, but it was still a point of contention for years.  I love my last name--it's unique and interesting, and I plan to have it for the rest of my life.  And if I were a man, I wouldn't even need to explain this.

Marriage is a patriarchal tradition in itself, what with it being a way for fathers to transfer their daughters from their property to their new husband's property back in the day, but that doesn't mean it isn't still relevant.  It's so relevant that legalizing gay marriage has been a massive and passionately-fought fight and is finally starting to be accepted in a number of states (way to go Washington and Maryland!).  I think that gay marriage's mere existence may help to take some of the patriarchy out of marriage--hold your horses, conservatives, that's a good thing--and make it a more egalitarian tradition.  So many things about weddings and marriage leave the two people involved on non-equal footing based on sex, and maybe that can change now.

The name change is the first symbolic act of submission in a long line of real acts of submission a woman is expected to perform within a marriage.  She is literally her husband's now; he didn't have to take her name to prove that he was hers but she sure had to prove she was his.  As awesome as my boyfriend's last name is, it's not mine and it never will be.  And fortunately, he could care less about that.

Yes, it's a red flag when your man cares about the keep-or-change question.  I know Cosmo will tell you that you should never bring up marriage on the first date, but for me this one's a dealbreaker.  Even if it's asked as an entirely hypothetical question, I tend to bring up the name change question on the first couple of dates because it is indicative of so much more than what's on the surface.

Anecdote redacted as requested by the person it's about. Let's just say I know someone who felt pressured to change her name against her instincts.

Now, I'm not saying that changing your last name upon getting married is bad.  I am a strong believer in the "I choose my choice" school of feminism, and if that is what makes you feel good about yourself you change that name.  I considered taking a previous boyfriend's name if we ever got married simply because it was so damn cool.  The problem comes when you change it because you're bowing to pressure from your future husband, his family, your family, or anyone else you know.  They can judge you all they want, it makes you just as committed to your marriage as any man should ever be considered to be.

Of course, as a last thought, this leaves open the question of who gets to give their last name to the kids.  I have made a hard-and-fast rule that boys can have the husband's last name and girls ca have mine and that's fine with me.  Lots of people go by the coin-flipping method.  A lot of people hyphenate, which is great but which would never work wit my already four-syllable-long last name.  I like the idea of leaving it up to equal 50/50 chance who gets to pass on their name.

I'm going to talk more about feminist weddings next week.  In the meantime, there are some interesting articles on this site about that very topic that you should check out.

Oh, and lastly, the boyfriend and I saw CMU's production of Sweeney Todd last night.  I would highly recommend it, if you get the chance you should definitely go see it!