#REVIEW: The Rouse, by China Miéville

I’m not gonna lie. Y’all, I have no idea.

I assume I’m not the only person who does this; when I am reading a book I know I’m likely to write a review of, I read it with that eventual review at least somewhat in mind. I’m not always likely to take notes or anything like that, but bits and pieces will jump out at me and I’ll stick them in the blog-part of my brain to discuss later.

The problem is that I could say literally anything about this book and I’m pretty sure it would be true. I hated it and it was brilliant. I loved it and it was exhausting. It’s got a complicated, detailed plot and it makes no fucking sense at all. I cannot tell you, as I’m sitting here, whether its central mystery was ever resolved, as it’s entirely possible that it was resolved in such an oblique manner that I missed it. Bits of it are, literally and without a trace of sarcasm or exaggeration, gibberish. At least six different languages make their way into the book, none translated, some not in Latin characters. There are two different main fonts, at different sizes. I don’t know what percentage of the words in this book Miéville straight made up but whatever you’re thinking it’s way higher than that. The book is largely dialogue, mostly of the circumspect and elliptical variety, but there isn’t a single fucking quotation mark in the book and sometimes it’s very difficult to tell who is talking or whether someone is speaking or thinking, and sometimes that’s because the characters themselves do not know if they’re thinking or speaking out loud.

One of the main characters spends a couple of chapters kidnapping children, exposing them to eldritch horrors, and returning them to their parents. The eldritch horrors in question: a literal ghost under a white sheet. The other’s vaginal secretions are more important to the story than vaginal secretions have ever been in a book before. She also occasionally drips from other orifices.

If China Miéville had not written this, I would never have finished it. But no one other than China Miéville could have written the fucking thing in the first place. You should pick this book up if and only if you are already a big fan of China Miéville. Not “I liked the Bas-Lag books.” You should pick this book up if and only if you have reread either Kraken or The City and the City, on purpose and of your own free will. And if that is the case, you already own it.

It is 1260 pages long and you will not have any idea what is going on the first time you read it. Expect to have to read it at least twice. There are four hundred and sixty-seven characters and they all go by their last names and one of them changes his name midway through the book for a reason that technically is given on the page but still doesn’t really make a whole lot of sense. The lead antagonist might be Satan. The lead antagonist also might be one of the main characters. Or one of their friends. I’m really not sure.

The following is the entire “Plot” section for this book on Wikipedia as of 7:54 PM on September 29, 2026, and at least one of these sentences is not true:

The novel revolves around the suicides of multiple British army soldiers. It is set during the Cold War.

I’ve tried to read some “professional” reviews of the book; most of them are paywalled, unfortunately, but I did read one where the reviewer was honest enough to admit that he doesn’t have any idea what the fuck the book was about either. He still recommended the book. I get it.

I gave it three stars on Goodreads and Storygraph; it cannot be ranked using such a pedestrian manner as stars.

The physical copy of the book is really fucking cool, but I read it digitally, because a lot of time I read laying down and I would have broken my nose on this fucker at some point.

I’ll write another review after I read it again. When will that be? I have no earthly idea.

#REVIEW: Angel Down, by Daniel Kraus

Every time I say this, I expect to get some pushback from someone, and I never do: World War I was a war that was fought for absolutely no reason at all, and every single person who died in it died for nothing. World War II is widely regarded as The Last Good War; its predecessor may have been the most wanton waste of human life I’m aware of. It was fought at a time where the technology to kill people far outstripped the technology to defend them, and every single thing about it was horrible.

Daniel Kraus, author of Whalefall, has written a book about World War I, where a group of American soldiers discover an angel dying in the mud in no-man’s-land between American and German positions. I read Whalefall when it came out in 2024, and I was surprised just now to discover that I five-starred it when I read it; my memories of it are not especially positive and I was expecting to discover I hadn’t liked it very much. I almost didn’t pick this book up, and then it won a Pulitzer, and FOMO kicked in, and to hell with it, it was cheap.

But I didn’t almost not buy it because I didn’t like Whalefall. I almost didn’t buy it because the book is structured as a single sentence, 304 pages long.

And the thing is, call me a philistine if you want, I’m generally not fond of people who try to fuck with structure too much in books. I like my narratives straightforward and my narrators reliable. I like dialogue to have quotation marks around it. I like all the text in a book pointed the same way. And I like sentences and paragraphs to be reasonable in length. I like a good long sentence once in a while, anyone who has read me for more than a few days knows that; 304 pages is Too Long.

So here’s the good news: if you have avoided this book because of the single-sentence thing, it’s absolutely a gimmick, and it’s almost unworthy of the book, to be honest. Here’s a randomly-chosen two-page spread:

You will note that there are, if not precisely paragraph breaks, certainly gaps between clauses that serve as such, and note the image break in the top left as well. The book also has chapters. Now, you’ll also notice that every paragraph starts with “and,” which you should expect to see a lot of, and all of those “paragraphs” end with commas, so technically this is all one sentence, or at least part of it.

But, c’mon. One of the reasons for paragraph and sentence breaks is to give the eye a place to rest, and the commas do that perfectly well. You will not notice, as you’re reading, that this book is one long sentence.

You will also notice that it never slows down, and it never lets up, but that’s more a function of the writing than the structure. Kraus could have sprinkled periods at reasonable places throughout this text without changing a single word and the character of the narrative itself would not have changed one whit. And, honestly, read those few paragraphs, and you’ll know whether you want to read this or not; follow that instinct.

I will say that I did really enjoy this book– it’s not on my 2026 shortlist, but if there’s going to be a book that sneaks onto my end-of-year list without having been on the shortlist, this will be it; it just depends on how well it sticks with me. It’s a better book than my recollection of Whalefall, certainly, and I suspect if I reread Whalefall tomorrow I would still think so. The sheer hopelessness of the WWI setting and the idea of saving a downed angel was a good enough high concept for a book to begin with, and the voice of the novel is perfectly matched to the setting and the characters. There’s also one other narrative trick in the last part of the book that I’m not going to spoil but which works very well; the book ends perfectly.

Well, sort of. You’ll see when you read it.

I have another Daniel Kraus book on my TBR shelf, one that just came out; he wrote a science fiction novel called The Sixth Nik, which means I’ll have read three of his books and they’ll have been from three wildly different genres. I know he’s got a ton of other books; Nik will determine whether I start seeking out his back catalogue or not.

#REVIEW: The Kindly Ones, by Jonathan Littell

This had better be the worst thing I read this year.

More on it later, possibly, but I have a terrible movie to watch before I talk about the terrible book. Needless to say, I have no idea who Michael Korda is, but I don’t believe he even read this fucking thing.

#REVIEW: Cursed Daughters, by Oyinkan Braithwaite

This is going to be one of those reviews where I talk more about myself than the book, so … brace yourself, I suppose.

I frequently make snap decisions about books. I learn of their existence and thirty seconds later money has left my bank account and a couple of days later I have a book. The problem comes when I don’t read that book immediately, and it gets worse when it sits on my Unread Shelf for four months.

(There are two books on that shelf that have been there longer. Soon. I swear.)

I have no idea why I purchased Oyinkan Braithwaite’s Cursed Daughters. No idea if someone recommended it to me, if I came across the author on BlueSky and decided I liked her … nothing. And by the time I got to it, I’d also completely forgotten what the book actually was. See, that cover kinda yells “fantasy” at me? And the book has the same physical format and size as every hardcover YA book I’ve bought for years. And note the “from the author of” at the bottom. Come on! You’re telling me My Sister, the Serial Killer somehow isn’t genre fiction??

Cursed Daughters is not a fantasy novel and it is absolutely not YA. It is, in fact, hated Litratcher.

It’s fucking brilliant.

I keep saying this, over and over: you should read more books by Nigerians, goddammit. The book scene out of Nigeria is amazing right now.

This is the second time this year I’ve had to apply the word “brilliant” to a work of genreless Literary Fiction. I remain salty about it. Because this is the only book I’ve read this year that came close to Tom’s Crossing. I need the swords and lasers and magic contingent to step up their damn game, is what I’m saying.

At the beginning of the book a Nigerian woman intentionally walks into the ocean to die. The same day, her cousin Ebun gives birth to a daughter. The baby resembles the dead woman, Monife, to such a degree that Monife and Ebun’s mothers immediately decide that the baby is Monife reincarnated. Ebun is … unconvinced, and frankly quite a bit upset by the entire thing. There is also the minor matter of a generations-old family curse, that no woman of this family can be happy in love.

It’s still not a fantasy book. There’s some traditional beliefs mixed into a book set in the modern day in Lagos, and there’s a juju woman as a minor side character, but it’s not a fantasy book. Ebun believes none of this nonsense, and her daughter Eniiyi wants nothing to do with it either, but has to live her entire life in her dead semicousin’s shadow. She dreams of Monife occasionally, and by the end of the book genuinely resents the effect on her life that this woman she’s never met has. She remains Monife’s spitting image, so when she occasionally runs into people who knew Monife she either provokes shock or is genuinely thought to be a ghost. And as her great-aunt gets older, she begins regularly mistaking Eniiyi for Monife, and eventually her dementia increases to the point where she forgets Eniiyi exists at all.

The book follows three generations of the family, with Ebun and Monife in the middle, and jumps back and forth from the nineties to modern day. You eventually learn why Monife chose to walk into the water, and I’m not going to spoil anything but God damn does it end well— like, “I gasped and had to put the book down for a minute” well. I started this yesterday afternoon, read a chapter or two and put it down. When I picked it up again in bed last night it cost me at least an hour of sleep, and I got home from work today and sat down in my chair and didn’t get up again until I finished it.

Absolutely phenomenal work. I ordered My Sister, the Serial Killer about ten minutes ago. It’ll be here tomorrow. Oyinkan Braithwaite is on my “buy immediately” list forever now, and I’d really like to know what the circumstances were that brought this book onto my radar. If it was you, thank you very much.

#REVIEW: Tom’s Crossing, by Mark Z. Danielewski

Buckle in, as this is going to be a bit meandering, but you’ve no doubt read my book reviews before and know to expect some degree of that, and frankly “a bit meandering” is a fair description of large parts of Tom’s Crossing anyway.

We’ll start with this: I bought this book out of spite. I don’t know anything about Mark Z. Danielewski as a person; as far as I know he has no social media presence, or at least I’ve never encountered anything from him, and I’ve never read an interview or anything like that. My only previous knowledge of his existence was from his book House of Leaves, a book I have never read and I kind of hate. The reasons I hate House of Leaves are probably not something I need to go into too deeply for this post, but I will give some brief notes:

  1. That the word “House” is supposed to be in blue; note that that is the case where the book is mentioned on the cover of Crossing up there.
  2. That the book frequently has blocks of sideways text;
  3. That the book’s fandom is excessively incel-coded and are very much the type of people who will recommend House of Leaves to you no matter what kind of book recommendation you have asked for. Dark fantasy? Have you read House of Leaves? Potboiler romance? Try out House of Leaves. 1940s etiquette manual? Let me tell you about House of Leaves.

These three things combine to make this book a big nope for me even if I might like it otherwise. I particularly refuse to read it because reading it might, somehow, make one of its fans happy, and I don’t want to do that.

A second thing: I like big books and I cannot lie. I currently have three other 1000-plus page books on my TBR, and at 1,232 pages I am pretty certain that Tom’s Crossing is the longest book I have ever read— Brandon Sanderson’s Wind of Truth has more pages, but the text on Crossing is smaller and denser and I’m pretty sure the wordcount is significantly higher. I saw this book in Barnes & Noble, thought “Oh, shit, Mark Danielewski wrote a new book,” then made the mistake of picking it up and noting the length and all the sudden I owned it. It is possible that I bought this book out of some bizarre need to stick it to House of Leaves, which is an inanimate object and does not have feelings.

This, an excerpt from page 34, is what you should expect from the prose in Tom’s Crossing. Yes, I read this on my Kindle; I bought the hardcover and then checked the book out from the library, because I’m not holding that huge fucking thing in my hands for twelve hundred pages.

Note a few things:

  1. There is not a single gerund in the book that ends with -ing. The g is dropped on every single one, including gerunds that are nouns; this book is very concerned with horses, and the word “geldin” really got on my nerves for some reason.
  2. Excessively long sentences. There are only nine sentences on this page, and sentences that take up entire pages or the majority of one are far from uncommon.
  3. That the narrator is the most highly-educated hick in the history of Utah. The dialect leads you to expect a certain kind of prose and then the book hits you with at least gettin a taste of a place where the bonds of birth and fortune have loosened their hold.

I rather expected to hate this book, to be honest, and I was hoping to hit something objectionable enough within the first couple hundred pages that I could put it down. By page 34 I was griping about it on a Discord I’m a member of. Around page 75 the language clicked.

This is one of the best fucking books I have ever read, and guys, I am so salty about that.

I am normally a Story Guy. I am a Setting Guy. I am rarely a Character Guy and even more rarely am I a Prose Guy. The story for Tom’s Crossing is serviceable but simple— it’s a Western, and it involves fulfilling a final promise to a dead friend by freeing two horses that are destined for slaughter. The main character is a teenager named Kalin, and his friend Tom tags along with him for most of the journey despite being dead. Tom’s sister Landry also comes along; she is not dead, at least most of the time. (Nearly every character in the book spends some time being dead, for the record.). Along the way the two get framed for a murder by the wealthiest family in town, the Porches mentioned in the above excerpt.

The setting? Sort of Utah, although it’s not our Utah, and the now of the book is also sort of the future, I’d estimate around 2045 or so, although the story being told is set in late October of 1988. Why is it not our Utah? Well, there’s some simple stuff, like there being a town in our Utah named Provo but none named Orvop, which is where the book is set, and then there’s weirder stuff like renaming Joseph Smith to Joseph Mith, which I thought was a typo for a while until it kept happening. Many of the book’s characters are Mormons, as you might expect from a book set in Utah, but the word “Mormon” is never used, although there is some criticism of The Church toward the end of the book. (Danielewski is not a Mormon, but apparently spent a good chunk of his youth in Utah.)

Also, when things that feel like specific references to Mormonism come up, they’re often changed too, beyond just the Joseph Mith stuff. The angel Moroni is renamed, and there are occasional scriptural references to books that don’t seem to exist. I actually went and found my copy of the Book of Mormon to check a few of the references; they aren’t in there, I swear.

Also, it appears that everyone in the world is fully conversant with all of the events in the book, even the ones that they would have had to have been present for; the book frequently cuts away to provide comments from random other people like the Reed Beacham mentioned above. Adding to the weirdness, nearly every time one of these random people is brought up, the book mentions how they died.

I also have the feeling that if I knew the Iliad and the Odyssey better I’d have picked up on some stuff. It’s been a while since I read either. This isn’t some kind of clever conjecture on my part; there is at one point a several-page conversation between three people about which characters in the book line up most precisely with characters from the Iliad. The book interprets itself. It’s nuts.

It’s the prose, y’all. I could bathe in this book’s language. About once every page or two Danielewski will hit you with a sentence or a phrase that will literally stop you in your tracks with its beauty. It’s 1200 pages long and I read it in eight days, during most of which I was also tearing apart my house.

I suspect I’m not quite smart enough to fully appreciate what’s going on in this book, to be honest. There’s a reason I make fun of Litratcher so often around here; I dislike pretentiousness in general, and while I’m very much not a The Curtains Were Blue guy, I also like my narratives nice and straightforward. I am not, as I frequently admit, the world’s most careful reader, and in fact the speed I read at frequently hurts me on more complex books. But, God, once this one had me, it had me, and I’m so glad I didn’t cave to my baser instincts and put it down after the first 40 pages just so that I could say I’d tried.

The worst thing? I think I might have to read House of Leaves now. And there is literally no higher praise that I can imagine giving to a book than that it made me decide to read House of Leaves.