Crucify Him!
When the only way forward is through.
Somewhere here on Substack in the past fews days I came across an article about the deeper meaning of the crucifixion of Christ. Deeper than He died for our sins, so we’ll all be forgiven. It blew me away, but can I find it again? Nope.1
The gist of it was something like, to progress morally, there is no going around or under or over; there is only suffering through. A lot in the current world news feels like that these days; there’s a lot of suffering but no getting around Ukraine, Gaza, Cuba or now, quite possibly, Iran. There is only going through. And it is painful.
The world was not always like this, at least not on the face of it. But we know how we got here, who made it so.
Many Americans marched recently in the No Kings movement. Whatever misgivings I may have about what they actually want, like maybe a “good” King (or Queen) as opposed to what they have, I agree they have a point. The guy’s gotta go.
Every kind of “regime change” entails a crucifixion of some sort. Somebody is going to get hurt. Which brings us to here…
Afterthought
We are also in the Jewish religious period of Passover, which overlaps almost exactly with Easter this year (but not always). Passover has a very different meaning — it celebrates the passage of the Jews out of slavery and out of Egypt — but thinking about the Crucifixion of course also brings up the fact that Jesus was a Jew, and the people calling for his death were Jews. Or so we’re told. It was, as they say, “complicated.”
The decision-making around the “trial” and sentencing of Christ is crazy. Read this account on Wikipedia. It reads like a Trump impeachment process, which only lacked the capitulation to the rabble at the end.
Losing really great finds on Substack happens to me so often. I do “save,” I reStack, I comment, and look in my Saved folder and Activity roster, and yet, still, I’m scrolling through so much, so quickly, I lose track of things. I will keep looking. A search of Substack for the term “crucifixion” returned this, which is not it, but pretty darn good:
