
Happy Tuesday, bibliophiles!
The ranting hour is upon us…yet I didn’t hate the book I’m reviewing today. It’s not abject hatred, more just frustration. Maybe I am a good-for-nothing Gen Z-er with no attention span, but I feel like if you don’t get into much concrete worldbuilding until the halfway point of a nearly 600-page book, that’s a real crime in your writing. Unfortunately, The Book That Wouldn’t Burn is guilty.
Enjoy this week’s review!

The Book That Wouldn’t Burn – Mark Lawrence
At a young age, Livira was kidnapped, then rescued and delivered to a sprawling city. Within that city was The Library, a building with layers upon layers inside, containing an archive that spans thousands of years. Now focusing on the education she never had, Livira will discover secrets that will change her world forever.
Evar has lived his entire life trapped inside of the bowels of The Library. Hunted by monsters, he was orphaned at a young age, and his siblings have slowly been picked off as well. With no escape in sight, he spends his days desperately looking for a way out—and he cannot see one until he finds a lost girl named Livira.
TW/CW: kidnapping, loss of loved ones, blood, violence
DNF at 44%.
I know I often gripe about long fantasy novels taking eons to get to the point, but this pushed it to the extreme. All of the rave reviews kept swearing that there was some massive payoff to the excruciating trek that was this book, but the intangible promise of something wasn’t enough to keep me going. The Book That Wouldn’t Burn felt stuffed to the brim with plot lines of no substance or development, and it’s not like the book was too short to be cut down. 571 pages. There were absolutely some chapters that had no business being there.
Suspense and worldbuilding are story elements that normally aren’t confused, but it seems that Lawrence got them mixed up in the construction of The Book That Wouldn’t Burn. It’s one thing to have a crucial element of your world be a secret—that was what the novel hinges on, and from the looks of it, understandably so. This technique is mainly for elements that will change the way the reader and the characters perceive the world. Lawrence’s problem was that he applied that to almost all of the worldbuilding. We get a brief glimpse of the outside world, but not much is known save for the divisions between humans and sabbers (a hostile, dog-like species), and that there’s a Vaguely Medieval Epic Fantasy Town™️ outside of The Library. I get that the focus is on The Library, so what’s the point of establishing any of it if it’s not going to be of any consequence later on in the book? Granted, I didn’t finish it, but the way it was written was so hasty. I did get some semblance of how The Library works, but it was too little too late. If you dangle some reveal over the reader’s head the entire time, you should at least have some information about the world to scaffold why you should care. To some extent, I can see that since all of this was foreign to Livira, but that’s not an excuse to barely describe anything!
I wanted to like Evar, but in the end, his situation was more compelling than who he was as a person. That’s because he’s a walking case study in why tragic backstories don’t automatically make a character fleshed-out. We know all about how he’s been trying to claw his way out of the catacombs of The Library and has been hunted by monsters who have killed his parents and many of his siblings…but we know nothing else other than that. Aside from an implied resilience on the virtue of him being able to survive being trapped in a monster-filled maze beneath a library, I know nothing about this kid. We are given exactly zero hints about his personality. I felt pity for him because of his circumstances, but I put down this book knowing nothing about what makes him tick, other than a vague semblance of revenge. I don’t know why he speaks the way he does, I don’t know his habits, I don’t know how he interacts with the world. I wanted to know him! His relationships were solely defined by their proximity to other people (many of whom were dead). By the time he finally met Livira, I couldn’t care less about how they would interact—mostly because Livira got sucked into some Library portal right before anything of significance could happen. 250 pages, about a third of which were devoted to Evar, and I just could not care less.
Now, for why I picked up The Book That Wouldn’t Burn in the first place…The Library. Again, this could be a consequence of me not reading enough of the book, but I think there’s merit in saying that there’s not nearly enough focus on what’s actually interesting about it for the first half of the novel. After the initial revelations that a) Livira now has access to a library the size of a city with archives spanning thousands of years and b) that there are people trapped in a monster-filled maze beneath it, we get…nothing else. There’s much more focus on Livira’s education in The Library, mainly because when she comes there, she does not know how to read or write. That wouldn’t be a bad thing if it weren’t for the fact that these scenes are repetitive to a fault. Remember what I said about this book potentially benefitting from some hedge trimming? This is precisely where I would slim down the page count. I don’t ascribe to the belief that every little thing has to advance the plot, but you’ve got to have something to keep the reader’s interest—it felt like the same cycle of Livira reading, writing, and getting teased by the apprentices. Rinse and repeat for approximately 100 pages. Now do you see why I quit?
The lesson of The Book That Wouldn’t Burn is that you can’t hold a book afloat on a concept alone. I wanted to like the premise so much—what’s not to like about a massive, age-old library that’s larger than a city and holds unknowable horrors beneath it? But the scaffolding necessary to keep me interested was flimsy at best. Lawrence’s writing had moments of being clever, but that, along with the shaky bits of information about the library, were not enough to hold my interest. 1.5 stars, because it wasn’t all bad, but I was so painfully bored by a book with a fascinating premise, which is truly a crime.
The Book That Wouldn’t Burn is the first novel in The Library trilogy, followed by The Book That Broke the World and The Book That Held Her Heart. Mark Lawrence is also the author of several fantasy series, including The Broken Empire trilogy (Prince of Thorns, King of Thorns, and Emperor of Thorns), The Red Queen’s War trilogy (Prince of Fools, The Liar’s Key, and The Wheel of Osheim), and many more.
Today’s song:
That’s it for this week’s Book Review Tuesday! Have a wonderful rest of your day, and take care of yourselves!




