This is my first post on GF. I’m new to the idea of feminism and still have a hard time identifying with – even thinking about! – the subject, and sometimes envy the ease with which the other writers here seem to be able to address the topic. But I figure that perhaps there are some others in the same place. And so I’m trying to drum up the courage to write about my stumbles through this, in the hopes that it’ll help me learn, and maybe help other people learn as well.
Inspired by this post on Long story; short pier about Erdos.
As a high school math geek (being on the math team at IMSA – the math and science magnet for the state of Illinois – was sort of like being a football player at Notre Dame, except without the cheering crowds at meets), I loved the story of Paul Erdos. On more than one occasion, I decided this was how I wanted to live when I grew up. On more than one occasion, friends in high school, and later college, would tell me (without knowing I had been thinking about it) that this was what I should do when I grew up, too.
“He would not stay long in one place and traveled back and forth among mathematical institutions until his death. Possessions meant little to Erdős; most of his belongings would fit in a suitcase, as dictated by his itinerant lifestyle. Awards and other earnings were generally donated to people in need and various worthy causes. He spent most of his life as a vagabond, traveling between scientific conferences and the homes of colleagues all over the world. He would typically show up at a colleague’s doorstep and announce “my brain is open,” staying long enough to collaborate on a few papers before moving on a few days later.” –Wikipedia
Remember, this was the age (14-17) at which my love of fantasy and sci-fi was rising dramatically – I’d always loved the genres, but those years of geek-fueled adolescence sent that love explosively rocketing upwards. Erdos was a wandering adventurer whose magic was mathematics, whose innkeepers were research colleagues and their families, and whose boss fights were against tough problems. When he won, the enemy would drop a Scroll (which looked suspiciously like a published scholarly paper) and Erdos and his party for that fight would add the spell (the proof described therein) to their inventory. He was my hero of a thousand faces.
“A hero ventures forth from the world of common day into a region of supernatural wonder: fabulous forces are there encountered and a decisive victory is won: the hero comes back from this mysterious adventure with the power to bestow boons on his fellow man.” –Joseph Campbell, from The Hero with a Thousand Faces
A hero ventures forth. He has to leave home, and the outward journey becomes a metaphor for that inner transformation and the mechanism by which a hero seeks and finds the experiences that help him grow. And of course one could be a heroine and go off and do exactly the same things – okay, it was less common, but the use of the masculine word was just historic and incidental, girls could grab a sword and sneak out the window and go off into the swashbuckling great beyond as well. No problem, never bothered me. Sure seemed a lot more fun than the alternative.
“In The Odyssey, you’ll see three journeys… the third is of Penelope herself, whose journey is… endurance. Out in Nantucket, you see all those cottages with the widow’s walk up on the roof: when my husband comes back from the sea. Two journeys [Odysseus and Telemachus] through space and one [Penelope] through time.” –Joseph Campbell
What did that tell me? Strong women wait? I knew I didn’t have the patience; I was young and a high-pass filter and wanted a sword now. Stories with quests and swords were celebrated; they sounded cool. Way cooler than the widows-walk adventure format. Walk a (metaphorical, in Penelope’s case) roof, raise a kid, fend off suitors trying to convince you that your husband’s dead. Big whoop – I didn’t want to walk a journey of endurance. I knew inside that it may be just as hard (or harder) or take just as much bravery (or more) to spend years pacing that widow’s walk than it does to spend those years on the high seas, avoiding sirens, blinding Cyclops, and the frequent application of the good old-fashioned “take your sword and stab things” tactic. But young people are high-pass filters, and I wanted (and still want!) to swing that sword.
And mostly, I kind of did. Being young and excited and extremely stubborn makes you unaware of a lot of things, especially the ones you’d rather already ignore. But now I wonder: does every Odysseus create a Penelope? If I become an Erdos, then who pays for my freedom other than me? Is privilege a zero-sum game?
And if it is, then who the heck am I supposed to follow?
That last line was originally the ending of this post. When I shared the draft, I didn’t feel like it was done; after some conversation, I was asked what I had hoped to get from asking that question, and the answer below was what I gave.
The example that pops to mind is the way I thought about… say, husband/wife relationships, a couple years ago. I’m from a pretty traditional Chinese Catholic family, and the only kind of marriage I’d seen was the type with a dominant breadwinner and a nondominant caretaker. Wonderful, loving relationships that both sides had consented to and all that – I don’t think my mom and aunts would have chosen any different, or if they could – you can’t choose something if you don’t know it exists, too.
I knew intellectually that more configurations must be out there, but I couldn’t really fathom what they were in anything except vague theoretical approximations that I knew to be unmapped against any sort of reality, because I’d just never seen them. I also knew I wanted to see more options before I started thinking about which, if any, I would maybe someday like to choose.
So when I went to college and met people – professors, older friends outside of school – who didn’t have a one-person-dominant other-person-not sort of relationship (I’d gotten the idea that those roles weren’t gender-specific, but they were still the same roles), it was one of those “oh, okay, that’s another way it could work” sort of moment.
Once I saw a few examples of things outside the paradigm that I was used to, I could think about it way more flexibly – these were different parameters you could set, and I’d just been exposed to one particular setting of parameters.
And with respect to the “is privilege a zero-sum game?” question, I’m looking for that kind of thing to happen again – I have a theoretical idea that other, non-zero sum configurations can exist, but… what are they?
A couple of years of not doing much Perl, and then coming back to it relatively fresh, is pretty eye-opening. Today I got some insight into what Perl is like for people who haven’t been doing it for years, and perhaps some understanding of why Perl doesn’t seem to be making many new converts.
I decided I was going to update one of my CPAN modules, the woefully unmaintained Metaweb.pm. I set out to do this on my work machine: a Macbook running OS X 10.5.5 (Leopard), on which I’d never done any serious Perl development before.
I started by checking out my code from my own repository. I was sure I’d need some stuff installed from CPAN, so I started by attempting to run the Build.PL that comes with my own module. It told me it needed a pre-requisite library (JSON), so I ran cpan install JSON.
Several hundred lines of text scrolled by, and it told me it couldn’t install anything. I dug back a fair way through a lot of non-specific “make failed” before I found anything approximating a meaningful error message: “Perl v5.10.0 required–this is only v5.8.8″. Fair enough. I need to upgrade my Perl. How do I do that on OSX? Well, I’m not sure, but I heard that perl.org had recently had a highly-acclaimed makeover, so I decided to check there. It tells me that Perl is included in Mac OS X. Yes, thanks. And upgrades? I couldn’t find binaries anywhere via the site.
A google for “perl 5.10 on osx” led me to perl.com’s download page which tells me:
If you want to upgrade, you can build the Unix source if you have the developer tools installed.
Luckily I happen to know that “the developer tools” means XCode, which provides such tools as make.
Hang on… wait a minute… how come I got so far without even having make installed? Surely the CPAN install script should have bailed out if there was no make? In retrospect, I realised that I’d just pounded blithely on the enter key while CPAN was configuring, and no doubt had skipped past the bit that asked me where my make was. I deleted my ~/cpan/CPAN/MyConfig.pm and ran through it again. Yup, sure enough, there was a warning. A single line, plain text warning, that I didn’t notice as it scrolled by.
Now, perhaps I’m just being picky here, but I’d expect that if there’s no make, it should fail a bit more loudly than that. But whatever. I went to download XCode, noting as I did so that nowhere had any error message or webpage actually provided a URL for where to get that, or even mentioned the name of it. Just so you know, here’s the XCode for OSX 10.5 Leopard download (binary file).
It takes me about 15 minutes to download the almost 1GB XCode via work’s network connection, but had I been at home, or worse yet back in Australia, it might have taken me hours. (It also comes on the Leopard install disks, but I don’t have them handy.) It was long enough for me to write this blog post up to this point, and if I hadn’t been fairly dedicated to getting the job done by now, I probably would have given up by now.
Another 20 minutes to install the package (during which I bitched to friends on IM), and I have make. I run cpan install JSON again and everything succeeds. There are 1,988 lines of output, of which many hundreds are Date::Manip’s file listing. Why do I need Date::Manip? I don’t even know, but that doesn’t stop it vomiting gibberish all over my screen.
Anyway, at long last I have the pre-req libraries I need to play with the simple, non-binary package I wrote two years ago. It took me a little over an hour in total.
Oh, and by the way, I didn’t need to upgrade to Perl 5.10 — I guess that was a red herring.
Recommendations
So, these are the things I think the maintainers of the CPAN module, and of various high-profile Perl websites, and of Perl itself, should be doing:
Some of these I can do something about, some I can’t. I’ll go nag the right people after I post this, and see if I can get things moving, write some patches, or something. But why are we even in this situation? CPAN has got hairier and hairier over the last, say, five to seven years, to the point where it is a serious impediment to anyone starting Perl development. If you are an experienced developer, you probably don’t notice it anymore, but trust me: I’d been doing Perl for a decade and been publishing modules to CPAN for eight years before I took two years off, and I found this intensely frustrating. For new developers on anything other than a traditional(ish) Unix system on which they have root (and that includes most web hosting providers), CPAN — which was meant to simplify Perl development — is undoubtedly a major barrier to entry.
This needs fixing.