16 Feb 2014
Adventures in scriptural revision
I was just reading 1 Samuel (that sounds like a lead-in that has a back-story, but it doesn't, really), and the footnotes in this edition (New American, i.e. Catholic) are remarkable. Here's one on verse 13:1:
A formula like that of 2 Sm 5,4 was introduced here at some time; but the age of Saul when he became king remais a blank, and the two years assigned for his reign in the received text cannot be correct. Tradition (Acts 13,21) offers the round number, "forty years".That is to say, we don't really know what this verse actually says, so we're leaving one part of it blank and actively contradicting another. This is how they actually presented that verse:
[ Saul was . . . years old when he became king and he reigned . . . (two) years over Israel. ]The brackets are included in the main text. The weirdness of this inspired me to check out a few other translations. For comparison, the NRSV has the similar
Saul was . . . years old when he began to reign; and he reigned . . . and two years over Israel.with two footnotes to explain the blanks. "The Message" Bible, a somewhat controversial idiomatic/contemporary translation, just sidesteps the missing numbers:
Saul was a young man when he began as king. He was king over Israel for many years.But what did they do before the era of modern Bible scholarship? Apparently, just say things that make no sense at all. Here's the KJV:
Saul reigned one year; and when he had reigned two years over Israel,What? And Douay-Rheims is even better:
Saul was a child of one year when he began to reign, and he reigned two years over Israel.What the what?
Just a few pages later, another footnote is even more eyebrow-raising in its sheer contradiction of the text. In 1 Samuel 15, Samuel (the judge, who speaks for God) says to Saul (the king), that it's time to punish Amalek; in verse 3, he says, speaking for God,
Go, now, attack Amalek, and deal with him and all that he has under the ban. Do not spare him, but kill men and women, children and infants, oxen and sheep, camels and asses.A gruesome, genocidal command, with no room for interpretation. But the footnote on this passage says:
In such wars of extermination, all things (men, cities, beasts, etc.) were to be blotted out; nothing could be reserved for private use. The interpretation of God's will here attributed to Samuel is in keeping with the abhorrent practices of blood revenge prevalent among pastoral, seminomadic peoples such as the Hebrews had recently been. The slaughter of the innocent has never been in conformity with the will of God.So... God gave a command, but Samuel edited it, and misinterpreted what God meant? An interesting idea; it might be worth pondering, except that the subsequent text pretty directly contradicts it. Saul, it turns out, carried through the full genocide but held back on some of the animals (not to eat them, but to sacrifice them later), and God doesn't like that he didn't wipe out everything:
Then the Lord spoke to Samuel: "I regret having made Saul king, for he has turned from me and has not kept my command." (10-11)Thence ensues a back-and-forth where it is fully clarified that when God says wipe them out, he means wipe them out, and wanting to offer sacrifices is not as important as obedience and submission. The closing line of the chapter reiterates that "the Lord regretted having made him King of Israel." All of which is, sure, part of the cognitive dissonance inherent in working with the Bible; and it can all be addressed with an analysis that understands Biblical history as an evolving relationship between humans and God. But that footnote is... well, the best that can be said is that it's trying a bit too hard.
'It should be a movie. A movie musical, in fact. That entire first book of Samuel screams out, "MAKE ME INTO AN EPIC. INCLUDE AN INTROSPECTIVE BALLAD."' --Jonathan PrykopPosted 10:44pm [+] | Comments (0)
27 Jan 2014
Ooh! Hate mail!
Well, that's new. I just got my first piece of hate mail attacking me for daring to take a stand against the old boys' club.
A couple days ago, someone posted to Hacker News about a new command line tool for looking up and curating examples of how to run different programs---a useful-sounding idea---which they decided to call "bro". The software is described at and available from bropages.org.
The term "bro" is, to say the least, one that comes with a lot of baggage. I saw the HN post fairly early, and in the first hour or two there were a couple comments critical of this naming choice and a lot of comments raging defensively against these criticisms. I made a post that tried to articulate just why the name was problematic; if you read the HN post about this my post is right at the top, having been heavily upvoted by many members of the HN community.
It also got a lot of responses.
If you have the time, you can read them; if you're familiar with this kind of argument there's really not a whole lot of new ground there. But that brings us to today.
Two days after the shitstorm in that comment thread, someone tracked me down (not hard, since I put my email in my Hacker News profile, although he used a different email address than the one I posted there) and emailed me the following helpful advice:
You are a huge white knight on HN. Do you really think that shielding women from the horrors of products with the word 'bro' in the name will get you laid? Pathetic. Most women need less 'protecting' than a dork like you.
I'd never heard of him before, but casual internet stalking (i.e. typing his name in a search engine) seems to indicate that he's in sales at a UK telco company; not clear if he would self-identify as a "bro" but it doesn't seem out of the question. By the standards of hate mail this is pretty mild, of course---when it comes right down to it, more amusing than threatening---but it's a bit puzzling what would be the goal of an email like this, other than to try to intimidate someone into silence.
Well, you can see how well that worked.
"I work on the assumption that Facebook is working by default to make me look like an asshole to everyone who's connected to me, because I've seen it do it to others." --John ScalziPosted 2:45pm [+] | Comments (0)