Reading Log 2019 #5: Babylon: Mesopotamia And The Birth Of Civilization, by Paul Kriwaczek

Writing a book about any aspect of the ancient Mesopotamian civilizations has to be a right bastard to begin with. Writing a book about ALL of them is basically a monument to hubris. That said, Kriwaczek does a very good job of tackling this huge span of history in his Babylon: Mesopotamia and the Birth of Civilization.

To put this in some perspective, the END of this book is as far removed from its start, in terms of years passed, as we are from the end of the book ourselves. He’s covering THOUSANDS of years here.

Starting with the first stirrings of civilization in the city-states of ancient Sumeria, such as Ur and Kish, and ending with the long fall of the Assyrian/Neo-Babylonian Empire at the hands of the upstart Persians, Kriwaczek takes us through what narrative we can construct from the available evidence.

And there’s a lot of evidence. There’s also a lot of gaps. The author’s job in such a case is to simply make sure the reader is aware of these factors, and Kriwaczek does a solid job on that front throughout.

Each chapter generally begins with a retelling of the archaeological dig that turned up the evidence that’s then used to provide the chapter it’s part of. It’s a nice way to let the reader know how confident the author is in the specific info he’s about to present.

As much as is possible, he includes details about the life of regular people as well as, of course, the ruling classes. That so much of the clay tablet-based evidence available is about economic and material transactions helps somewhat in this regard. We know more about how ancient Babylonian societies fed and clothed themselves than we do say early Ancient Greece or Ancient Egypt solely because their records-keeping took place in a physical format that could survive quite well for millennia, unlike any paper or papyrus-based writing systems.

This is shown by how much less data we have on the latest, Akkadian and Assyrian Empires that had converted to recording their language via an Aramaic, alphabet-based script on more paper-like substances that did not survive than we do on empires that existed a thousand years prior to them.

Kriwaczek also tries to tie a lot of how these civilizations operated to modern-day equivalents, which is… a stretch, to me. Sure, a lot of the evidence we have may relate to economic transactions, but making the leap from that to “they were obviously full market capitalists” seems a bit much. It’s a type of comparison the author makes repeatedly, and it never quite lands for me.

That nit aside, I like and recommend this book mostly because it’s engagingly written, and covers a vast territory and time about as well as any non-academic tome could in one volume.

Reading Log 2019 #4: Semiosis, by Sue Burke

Fun read, this. Classic sci-fi that takes a small group of plucky humans fleeing an increasingly ravaged and warred-over Earth to try again but better on an earth-ish planet elsewhere.

This new planet, which the colonists dub “Pax” (didn’t love that; a little on-the-nose), is juuuust-barely able to provide for the newcomers, at least under their original plan. Life is downright hostile, for the most part.

So, things therefore get weird when the younger generation of native-Pacifists (what the colonists refer to themselves as, in case the planetary name wasn’t clear enough for you that these folks are rejecting the violence of ol’ Earth and doing things differently) realize that their parents have set them up for suffering and are actively refusing to take steps that would make their lives materially easier to deal with on Pax. And, oh irony, are willing to use violence to enforce that suffering.

That may sound like spoilers but it’s not really, it’s effectively set-up and a good dose of world-building to get us situated in the environment and its unique properties that differ it from Earth (since it is alike in most ways). The actual Earth-born humans and their concerns are not the point of this book as Burke uses the enjoyable tactic of time jumps quite often to get us past the whole “struggling colony on the edge of disaster” thing that isn’t really the story she wants to tell. So, we quickly move along through a number of generations of the original Pacifists’ descendants, with each generation getting a star turn and a protagonist, though there’s plenty of overlap between chapters as well.

Books using this trope tend to suffer from the lack of a single protagonist for the reader to identify with, but that’s not a problem here. There IS one character who travels through the entire book with the reader, but I won’t spoil that… entirely

I will spoil it enough to note that it’s not an omniscient computer, a trope that exists in far too many books of this nature. Refreshingly, Burke acknowledges that, in the absence of the ability to bring along the entire industrial fabric that makes spaceflight from Earth possible in the first place, all of their computing and machining power will eventually, and not in TOO long a time, fail and become useless. This happens here, after a brief and expected period of cannibalizing dying tools to keep other ones going.  

I genuinely enjoyed this aspect of the story; the original settlement mission doesn’t happen TOO far from now, so there aren’t deus ex machina-style self-healing, self-replicating nanofactories or any of the usual suspects authors bring along when they want their tiny precarious space colonies to generally resemble future Earth as much as possible. In effect, the Pacifist society, for the bulk of the story, is at about a late medieval-level of technological advancement. They have their forebears’ modern knowledge, which certainly puts them above the level of actual medieval societies, but, lacking modern infrastructure, they can rarely act on that information, which to me is almost worse. Things are not helped by the great scarcity of mineable ores on Pax.

This is what provides the tension in the tale; the original colonists barely have enough folks to provide the basement level of Maslow’s hierarchy of needs, and for all of their knowledge and still-working computers, they’re still dealing with a very alien ecology that seems actively engaged in killing them.

This tension then turns, in later generations, to the Pacifists figuring out how to make accomodations with at least parts of their environment and to start to thrive, if never to the point of what the reader would understand as modern levels of physical comfort and material satisfaction. This culture seems to be pleasant to live in, but everybody works hard, and the random death of young, healthy people is a much more common event than it is for ours.

After setting all of this up, the book moves into essentially two primary conflicts, both of which are very enjoyable and which introduce concepts that aren’t entirely new to sci-fi, but whose extrapolations at the hands of this author are very fun to read. I don’t want to spoil those, but suffice to say that I’m greatly looking forward to the sequel.

That said, Semiosis stands as a complete story on its own as well, so don’t be put off by the fact that a sequel is coming. It ends at a good point, having wrapped the major points up but leaving the reader able to easily speculate any number of possible options to start new stories with in a sequel. It’s a solid basis for a universe of stories, but also a cohesive novel of its own.

I did have a few gripes, all of them pretty minor; characterization is mostly excellent, but a few characters were a bit one-note. The cast is large, given the time period covered, so of course not everybody can get a full fleshing-out, but some folks were pretty one-dimensional in a way that strongly hinted “I need someone like this to move this part of the plot forward, so here she is”. Again, though, most of the major characters were quite believable given the time available to spend on them.

Certain happenings also happened in time frames that just seemed entirely too short, but said shortness was obviously necessary for plot tension purposes. Explanations are given, but they don’t always land as completely believable. Also a minor issue, but one that had me swallowing some suspension of disbelief here and there.

Overall, though, this is a stellar debut novel and I eagerly await the sequel and what else Ms Burke has in store for us. 

Reading Log 2019 #3: All for Nothing, by Walter Kempowski

This one was recommended to me by a buddy who shares my fascination with Central Europe’s experience in the 20th Century. I consume a lot of fiction and non-fiction on this topic.

As I’ve gotten older, I find myself less interested in the march of armies or the words of politicians in this era; that story is exhaustively documented, and I’ve ingested enough of it to where I think I’m solid on that front. Now, I find myself much more interested in how regular folks got on (or, more often, didn’t) during these cataclysmic upheavals and their aftermaths. And All for Nothing falls squarely into that wheelhouse.

The book traces the story of a fading aristocratic estate in Eastern Prussia that is in the direct path of the final Soviet offensive that ended up ending the Third Reich entirely. Starting in January 1945 and carrying through into the summer, with tons of flashbacks as well, we follow the story primarily through the eyes of the 12 year old protagonist, Peter, who is apparently loosely-based on the author himself, though the book is fiction.

The story is intimate, and goes into obsessive, almost repetitive detail on what the family does to sustain and entertain itself during this period. Nursery rhymes are repeated in the text over and over, lists of possessions and foodstuffs appear on the regular, in great detail… the overall effect is to hammer home what was being consumed, destroyed, never to return in the all-encompassing fire of the Reich’s Gotterdammerung, all of the family and friend connections and rich material history that would be rendered into ash.

As the story proceeds, it is not just the family that is affected. Refugees fleeing the Red Army steamroller just east of the manor start appearing, and either choose themselves to ask for shelter, increasingly, are imposed upon Peter’s family by the Nazi potentate who is in charge of this district. We get to see how various classes of lives are affected by this calamity; these characters weave in and out of the story, first spending some time at the Manor and then being met again under even worse circumstances as the family itself finally flees home and joins the massive, hopeless exodus clogging the roads of East Prussia in search of an escape that is no longer open to most of them.

In the background but important are the various foreigners who didn’t exactly choose to be at the manor; from the Ukrainian domestic workers who were basically enslaved by Peter’s father as he performed his duties of brutal resource extraction for the Reich’s war machine and sent to do labor at his home, to the Polish POW who tends to the manor’s small farm and its animals, to the variety of POWs and forced laborers from all over occupied Europe who are stabled up the road in a former hotel and who become an increasingly (and understandably) menacing presence.

As should be needless to say, it’s not a pleasant story, there is no happy ending, and, by the later chapters, the tempo of Bad Shit Happening increases to the point that this reader was actually somewhat depressed upon finishing the book.

Kempowski is apparently a big deal in Germany. After surviving the war, the Soviets accused him of being an American spy and tossed him into prison for eight years before releasing and deporting him to the west. He spent the rest of his life writing novels set in this lost era, and embarking upon a project to collect the diaries and writings of East Prussians and their war experiences, which he did to the point of having to put an addition onto his house to store the collected materials.

This novel shows why he and his work is important. For very understandable reasons, the rest of the world isn’t inclined to get weepy over the fate of Germans in 1945. Large swaths of the planet was ash and rubble due to wars started by Germany and her allies, tens of millions were dead all over, and if a few of those millions were freshly-killed Germans, well, Jesus, wasn’t that just the bare beginnings of justice anyways?

Maybe yes. The point of this book isn’t to judge the suffering, it is simply to record it; it’s up to the reader to decide if any individual act of suffering or pain requires any further analysis beyond “this person is suffering”; the strength of this work and others like it is in forcing the reader to examine their own feelings on the nature of suffering; can it ever be deserved? Should it always be alleviated? The author here isn’t going to tell you one way or the other; his job is just to document that suffering happened.

Given that, I think the essential question this book asks of the reader is: is suffering quantfiable beyond “survived it or not”? Is a moment of extreme pain more or less worthy of a witness’ sympathy if we know that the sufferer themself caused great pain to others earlier on? If so, how far out do the circles of complicty range?

It’s a tough question with no clear answer; sure, it’s easy to say “fuck that guy” when “that guy” is a brutal Nazi functionary who has spent the entire war out of harm’s way behind the front ruthlessly stripping conquered peasants of their very sustenance if not killing them outright and he’s finally getting his just desserts; less so when it’s a 12 year old child caught in the gears of two insanely violent war machines meshing into each other.

The writing doesn’t demand that the reader come up with an answer either way; the prose is dry, matter-of-fact, and laden with description. While scenes of the characters experiencing sentiment are common, these are presented unemotionally, relying instead on a factual “these are things that happened” recitation that eventually becomes numbing. The first death of a major character (I don’t think it’s a spoiler in THIS kind of book to mention that death occurs) is presented so dryly that I had to reread it a few times to make sure that what was being described was what actually had happened.

There’s a weight to this kind of presentation; all of the dry retelling of individually unremakable happenings slowly turning into life-changing, usually for the worse, events, ends up creating a slowly-building atmosphere of just complete, oppressive dread in the reader. It’s clear that the other shoe, that ALL of the other shoes, are going to drop at some point, and by the time it does, ending the book in a basically non-stop parade of increasingly-worse horrors, you’re almost relieved to be getting on with it.

I liked this book a lot, but don’t know that I’d recommend it to anyone I care about and presumably would prefer to be happy than sad. It’s a sad book about a massive human disaster almost entirely brought upon the victims by their own complicitly in equally horrific, but different, disasters. And the book doesn’t even try to impute a moral or lesson to all of this suffering; it’s just a chronicle of it. At best, one comes away with a strong feeling of “we should do everything in our power to prevent anything like this from ever happening again”, but that is clearly a lesson lost to our current times so there is no solace to be found even in that.

Reading Log 2019 #2: Fallout, by Todd Strasser

I’m conflicted on this book. On the one hand, I generally enjoyed it? I think? I mean, I started it at like 9:30 on a work night after finishing my previous book and finished it at midnight the same night, so it definitely kept me turning pages.

That said, I also think the book could’ve been so, so much better.

The gist of the plot is: the Cuban Missile Crisis goes hot (note: this is NOT an alt-history of any sort so don’t expect any detail on how that all goes down or anything; the point is simply that it’s early-60’s American and the nearest big city to our cast gets nuked). The one guy in the neighborhood who had the foresight to build a fallout shelter in his backyard orders his family in as the sirens go off. The neighbors, who know about the shelter but did nothing but make fun of the family for being paranoid, bum rush his place and, after a struggle, some of them make it into the shelter with the main family.

The bulk of the story, then, is about how these people get on when forced to live in a dubiously-supplied shelter, particularly given that half of them forced their way in against the will of the guy who built it.

It’s a very small-scale story that focuses on the various pair-relationships between shelter inhabitants. Backgrounds on those relationships are provided via flashback chapters quite often, showing how those folks interacted prior to the bombs going off.

The story does best when focusing on the protagonist, Scott. He’s a nearly-teenaged boy, the son of the shelter-builder, who I identified quite a bit with. He’s a “good kid”, but his best “friend”, who ends up in the shelter as well, is quite not, and keeps trying to lead him astray. These tensions amp up in the shelter, naturally, and the author handles this relationship in particular with a deft hand. It reads honestly as a relationship that could’ve existed in reality.

Scott’s father is portrayed with a kind hand as well. He reads like a lot of dads I’ve known (though not my own): he means well, but lacks some of the tools, particularly in the empathy category, to be a truly-good dad. And a lot of his mistakes are effectively made against his own will and correct instinct, driven by societal pressure instead. After the bombs go off, the dude is in a truly shit situation, and he handles it (and this is a beef I have with the book in general) just about as well as anybody could. I’m not sure if this character is believable in extremis, but his pre-war characterization reads pretty true.

Some of the “bad” characters, however, are pretty ham-handed. Bad Kid’s father, in particular, is almost a caricature of an effete, college professor liberal of the nascent go-go 60’s, letting his kid drink wine at dinner until he’s hammered, leaving Playboys about, and sneering at his less-refined neighbors construction of a shelter in the first place. The guy sucks, in an almost unbelievable way.

Likewise, the women characters are pretty thin, the black housekeeper particularly so. They serve largely as props for the men to act against, even though they’re often the smartest people in the room.

My prime beef with the book is that it’s somehow too optimistic. I don’t think this scenario would or even could play out as neatly as it does; even given the death and conflict involved, it’s… not enough, somehow, given the enormity of the catastrophe that has obviously occurred to the world. I don’t want to spoil how it all plays out, but I ended the book with a pretty heavy sense of “well, that could’ve been much worse”.

Lastly, I want to mention that the book miserably fails the test of Chekhov’s Gun, which is always infuriating.

So, I dunno… I chewed through the book fast, it’s a page-turner, but I think I was turning pages mostly waiting for the other shoe to drop, which it effectively doesn’t. I also enjoyed the writing of the lead character enough to be invested in his fate, at least, if not of many of the others. If you like explorations of how people forced into extreme close-contact scenarios will behave, you’d probably enjoy Fallout, just know that it certainly lies on the optimistic side of the genre. Even though New York gets nuked.

 

Reading Log 2019 #1: Revolution: The History of England from the Battle of the Boyne to the Battle of Waterloo (The History of England, Vol. 4), by Peter Ackroyd

The fourth of five (so far) volumes in Ackroyd’s “History of England” series, Revolution covers, well… a lot of revolt.

Starting from the end of the Glorious Revolution that wiped the Cromwellian grimness out of power, continuing through the American Revolution, and ending with the English reaction to the French Revolution and its Napoleonic successor, Revolution stays on-topic with its title throughout. Oh, and let us not forget what was arguably the most important revolution of them all: the Industrial Revolution. Ackroyd presents the latter as more of a process than a singular event, but its impact reverberates throughout every other event in the book. 

I’ve liked the way Ackroyd writes since I first read his London: The Biography (a book I can’t recommend enough if you have any interest in any aspect of that city at all). While the scholarly rigor is fully present in the facts presented and sourcing and all that, Ackroyd is anything but dry. Broad-sweep views of the politics or background events of the day are interspersed with tight, personal vignettes drawn from the people being impacted by those politics and events. More academic chapters covering the government and wars and such alternate with chapters focused on the economics of regular people trying to get by, or on the arts of the era. It’s a well-rounded read that moves along quickly given how much it has to cover.

If there is a fault to be had with Revolutions, it’s in the conscious choice of the author to focus it tightly on _England_; you’re not going to get much discussion of the slave trade or India save as to how they directly impacted on the English in England itself. It’s emphatically NOT a history of the Empire. But, he’s clear about that in the very first volume, so it’s not so much an issue as it is just something to be aware of. 

Ackroyd also doesn’t cast much of a critical voice into the narrative, either; you won’t get much sense of how the author feels about any of the events he’s retelling. The lack of easily-discernible bias is honestly somewhat refreshing, but some sense of point of view would be appreciated by some readers, I’m sure.

That said, I like his approach and recommend this book and series to anyone who wants a deeper dive into English history than any single-volume book could do justice to. 

 

iPad Pro 11: Not For Portrait-Mode Thumb Typers

The new iPad Pro has been out for a little over two months right now.

I’ve bought three of them 😦

And they’ve all been returned at this point, and I’m using my trusty old iPad Mini 4 instead. Why? Well, I can tell you at least it’s NOT due to “bendgate” or anything; all three were straight as arrows on all sides.

But I still think there’s a manufacturing defect or design bug that affects iPads reliably, but only in a pretty rare use case that I unfortunately happen to be very prone to.

You see, I use my iPads in portrait mode 95% of the time. Yes, even the 10.5 and now 11 inch bigger ones (I have pretty gigantic gorilla hands). I’m often holding it up in bed or while sitting somewhere, and I thumb-type the shit out of that screen in portrait. This has worked just fine with every iPad I’ve had up to the new Pros. My primary uses with the iPad are reading books and articles, and reading/responding to social media shit, all of which I do mostly in portrait while thumb-typing. I don’t like having the screen far away from me on a desk or surface when I’m using a tablet; they’re personal devices to me, and I hold them up pretty close. My eyes are old to the point where I need a bigger screen than any iPad gives to be comfortable using it at laptop distance for any length of time.

The problem is noticeable right out of the box; when holding it in portrait mode and typing on the onscreen keyboard with my thumbs, the t, g, b, h and y keys (and sometimes the ones around those, but less so) will often make the keyboard click sound and depress on the keyboard (the two signs iOS gives the user to say “I acknowledge that you are pressing this key and want me to actuate it), but they will NOT enter into whichever text field I’m actually trying to enter into. Since I type fast with my thumbs, this quickly becomes a big problem. Every third “the” renders as “he”, “that” is usually “hat”… just an infuriating mess of easy to miss typos.

Since I’m one of those dinosaurs who hates to make typos, and likes correct spelling and grammar, this is obviously crazy-making to me. I write a ton on these things, and having to spend twice as much time laboriously using iOS’s editing features to correct typos than I did typing it out in the first place quickly became untenable.

I’ve since been to two different Apple Stores with three different iPad Pro 11’s that all exhibit the issue. One of the techs insisted on testing it with the iPad lying down on the table and couldn’t get it to replicate; they eventually gave me a senior tech who followed my instructions and held it the way I do when the problem actually occurs and it reliably triggered.

I suspect, but obviously can’t prove, that the little bit of extra thinness and the little bit of extra width on the 11 over, say, the 10.5, leads to just enough torque being applied when trying to portrait-grip this thing and stretch thumbs over to the middle of the keyboard to cause the digitizer to flex out of true just enough to break the finger-glass-digitizer-OS chain of events that leads to a character input actually being fully acknowledged.

The fruit stand techs probably get horse-whipped by the ghost of Steve Jobs if they give even a passing nod to a possible physical defect in a new product that hasn’t been acknowledged by corporate yet (see: the fucking MBP keyboards for first two years of this generation until, voila, Apple acknowledged that they just might have a shitload of issues), so he doubled-down on “it’s probably a software bug, keep an eye out for iOS updates that might address that and buy another one if you’d like at that time”, which is fine advice, but this really feels like a physical issue to me. There’s a slight chance I guess that the gyroscope is being knocked out of true in that orientation and pressure and that could be fixed by a software change to calibration, but I won’t be holding my breath.

I posted to Reddit and some other forums about this issue in early January after more Googling still didn’t bring up anyone else having this issue; my posts however, did bring at least a few people out of the woodwork to state that they were having similar issues. The gist seems to be, though, that portrait-typers are an increasingly dying breed and that, even if this issue is as widespread as me getting three iPads in a row with the problem seems to indicate, so few people actually use iPads in this precise way to trigger it. I blame my humongous neanderthal paws for even making it possible.

So, I’m bummed. I can either continue to use my ancient Mini 4 (which, to be fair and to Apple’s credit, works ridiculously well still, even if the battery life is pretty degraded; iOS 12 really rejuvenated older iOS devices to a crazy degree), or buy a previous gen 10.5 again, which, to a die-hard Apple PayPig such as myself, is humiliating*. I’m leaning towards the latter, as I really loved that device, it doesn’t have this issue, and even a refurb bought today will probably be good for 3-4 more years.

My main question now is wondering if this will slowly creep up enough across the userbase to actually become an issue Apple has to acknowledge and work towards correcting, or if this entire generation of iPad Pros is just going to be dead to me (which would crazy suck).

At the end of the day, it’s a super First World Problem, and Apple’s support and store staff were uniformly excellent throughout, giving me no hassle at all, even as I wanted to immediately open, try and return thousands of dollars worth of shit in their store. So that’s good at least. I’m imagining going through this with like a Samsung Tab S4 or something bought from Best Buy and just lol.

Anyways, please don’t Old Tech Shame Me if you see me out and about with my Mini or 10.5, I’d crumple up and cry if you did.

*might as well just drive a 1989 Chevy Citation while I’m at it

Apple’s Smartphone Dominance Explained In One Feature

I’m not partisan about mobile ecosystems; I’ve spent thousands of dollars on iOS shit over the years, and thousands on Android stuff, too. I like features from both and think that choosing between a goodAndroid phone (Google’s Pixel line, essentially) and an iPhone is something that comes down entirely to personal preference.

That said, I spend MOST of my time in iOS land. Why? There’s a million little quality of life things I think iOS does slightlybetter than Android, but I’ll talk about just one in particular that stands out as it’s a very good example of what Apple gets right that Android still misses the mark on:

Adjusting the brightness of the screen.

You know often I have to do this manually on my iOS devices?

Never. I literally cannot remember the last time I had to manually dim or brighten the screen on a device. They’re just ALWAYS at the right brightness level for whatever lighting conditions I’m in.

Out on my balcony on a sunny day? It goes full max brightness without me even noticing.

Lights out in bed at night when wife is already asleep? It dims itself to almost the lowest setting.

It just figures out what is the best setting for the moment.

In contrast, the last two Android devices I used (Pixel 2 XL by Google, and Samsung’s Note 9) ranged from “needed slight, but regular manual adjustment to the auto-settings” (the Note) to “this is just broken entirely” (the Pixel).

I had a couple of Pixel 2 XLs due to Google’s iffy QA and screen manufacturing woes this generation (another thing Apple gets better; the next bum-out-of-the-box iOS device I buy will be the first). Every one of them, I quickly ended up turning off Android’s Adaptive Brightness almost immediately because I can’t stand watching a screen change its own brightness constantly while I’m looking at it while stationary in an evenly-lit room.

I never notice my iOS screens adjusting themselves; they’re just always at the right brightness.

Again, this is the whitest of whines, the First World-iest of problems, but it’s something Apple a) realized was a low-intensity but widespread quality of life issue and b) iterated until it was fixed.

Like, I vaguely remember, many iPhones ago, manually setting a brightness slider because I read somewhere that iDevices like you to do that once or twice so it can set a baseline of what brightness level each person likes in a given ambient light scenario, and then it adjusts brightness against that from there. I feel like this is data it passes along with your iCloud profiles so it carries over from device to device, because I’ve never had to fuck with it again.

These kinds of things exist throughout the Apple ecosystem, and is the thing that keeps me coming back to them even when I’m seduced away momentarily every year by the latest Pixel phone.