A Week Later

It's been a week since the bombing attack on the Boston marathon, and if there's one thing you can say about the week, it sure wasn't uneventful.  First there was the bombing itself, on Monday afternoon.  I was working about a mile and a half away, and for a while I wondered if I was going to be able to get home.

On Tuesday, there was an explosion at a fertilizer plant in Texas.  This is unrelated to the Boston bombing, and as far as anyone knows, accidental, but despite the intentional terror and destruction in Boston, more people were killed and injured, and more property destroyed, in Texas.

It was late Thursday afternoon when the police released the pictures of the two suspects in the Marathon bombing.  That night, I began to hear things about a gunman at MIT.  At first this seemed to be unrelated.  I went to bed knowing that a MIT police officer had been killed, but thinking that it was the result of an armed robbery at a convenience store gone bad.

I woke up on Friday to find the whole city shut down.  The public transportation wasn't running, my work was canceled, and residents were being told to shelter in place.  It seemed that the incident at MIT had turned out to be the bombing suspects after all (though it doesn't seem as though they had anything to do with the convenience store robbery).  After which, they hijacked a car, and fled to Watertown, where they got into a shootout with police, in which they used explosives (early reports said grenades, but I haven't heard confirmation on that). One of the brothers was killed, but one fled on foot, and the police were conducting a door-to-door search.

Shelter in place didn't necessarily mean stay home.  Many people were out and about when the order came down, and were trapped where they were all day.  In addition, people were evacuated from their homes as the police searched, and forced to stay with neighbors and friends. I wasn't in one of the places that received that order, but I couldn't get to work either, so I pretty much stayed home all day.

They finally lifted that order on Friday evening, and then they found the bomber about an hour later, when a vigilant citizen noticed him hiding in the boat in his backyard (leading a few to wonder how helpful that order was in the first place).

The bombers were identified as two Chechens, Tamerlan and Dzhokhar Tsarnaev.  Both were legal immigrants who'd been in the US for years, and Dzokhar is a US citizen, and a student at the University of Massachusetts.  Right now the evidence suggests that they've been becoming increasingly interested in a radical form of Islam for the past couple of years.  It remains to be seen whether they acted independently, or if they had support--whether in material or training--of any known terrorist groups.

I've been reciting this mostly from memory, and mostly because I want to write down my recollection of it as accurately as possible.  Some more information about the case, and where things stand now, can be found at Boston.com.

Explosions in Boston today

I went down to North Carolina last week to attend my grandfather's funeral, where he received military honors, including a three-volley salute.  I was going to blog on that, and probably still will later this week.  However, something that affected more people than just my family occurred upon my return, namely the bombing attack on the Boston Marathon.

Around 3 pm today, two bombs went off at the finish line of the Boston Marathon.  At this point, it's not known who was responsible for the attack.  There are three dead so far, and over a hundred wounded, some critically, so that number may rise.  The Boston Herald has this to say at the moment:

Two huge explosions rocked the Boston Marathon finish line at Copley Square just before 3 p.m. today, killing three and injuring 134 at last count, including several traumatic amputations on streets crowded with runners, spectators and post-race partiers.

Many of those injured are children — including an 8-year-old killed in the blast, the Herald has learned. Boston Police Commissioner Edward Davis said tonight there is "no suspect" and the death toll is now at three.

It's being called terrorism, since it is by definition a terror attack, but it's not known whether  it's domestic or foreign, an individual or a group.  We'll find out more in the coming days.

This hits pretty close to home for me. While my wife was in Arlington all day, I was at work in downtown Boston when the attack occurred.  I didn't hear the explosion myself, but it was within a mile and a half of where I work.  Still, I missed most of the chaos, and things had settled down by the time I headed home.

What I don't know is whether anyone I know was hit by the blast.  I know people who were watching the marathon, and even a few people running in it.  So far, I haven't learned whether anyone I knew was injured, but it may be a while before I hear from everyone.

New Review

My latest review at Black Gate, of Dalya Moon's Broken Shell Island, is now up.  I thought the plot could have been a little more logical, but I liked the story overall.

The Alien

C. R. Wiley has an interesting post up concerning the different views of the alien as expressed by C.S. Lewis and H.P. Lovecraft.  It's a really long article, and I encourage you to read the whole thing.

But to give you a taste of how Wiley interprets Lovecraft's view:

Lovecraft believed he possessed greater insight into the nature of things than better-adjusted, healthier people. He took dark comfort in breaking the news to the rest of us that we are all as strange and out of place as he felt he was. He wanted to take his readers Outside, or, perhaps better, to bring the Outside inside. Here’s Lovecraft from yet another letter:

To achieve the essence of real externality, whether of time or space or dimension, one must forget that such things as organic life, good and evil, love and hate, and all such local attributes of a negligible and temporary race called mankind, have any existence at all. Only the human characters must have human qualities . . . but when we cross the line to the boundless and hideous unknown—the shadow-haunted Outside—we must remember to leave our humanity and terrestrialism at the threshold.

Meanwhile, Lewis sees things quite differently:

Because there is a “Wood Between the Worlds” for Lewis, creatures can be said to be beautifully fitted for their respective realms. Beauty does not merely reside in the eye of the beholder (although it certainly should reside there); it is recast. When prejudice and pride are cast away, the lines of alien beauty can come to the surface. Because the Wood Between the Worlds is common to all worlds, inhabitants from each world have the power to recognize the beauty resident in another world. This is not a species of relativism—it is classical Realism in a coat of many colors.

To a theist, all things are the product of God's divine purpose and grace.  They may be fallen and corrupted, but they must contain a spark of the divine, which gives beauty to even the most mundane or alien.

Reading and Writing

In a writers' forum I participate, the question has come up of whether writers really need to read.  The answer is yes.  I'm not one of those who say that a writer needs to read fiction in their genre every day.  You probably should read plenty of fiction in your genre, but I'll admit that I go through dry spells.  Sometimes I'm reading a book a week, and sometimes I may go months between reading books and even stories.  However, even given the occasional dry spell, I have amassed quite a catalog of books in my genre that I have read.  So even when a writer isn't reading a lot now, I would hope that he's read a lot in his formative years.

I sometimes think that I don't read widely enough, or read enough.  But even when I'm reading the least, I easily read ten times as much as I write.  So it's hard for me to comprehend how writers could hardly read at all.

Why is reading so important?  If you read a lot, won't your work sound just like everyone else's?  Well, yes and no.  Part of the reason to read a lot is so that you absorb the elements of writing.  At the most basic level, that's vocabulary and grammar, and how to put together coherent sentences and paragraphs.  How to describe a scene or an action.  Believe it or not, a lot of would-be writers have never learned, or at least are very rusty, with these basic skills.  They may have learned them in grade school, but a lot of people haven't practiced them since, and seeing how to use the language helps immensely.  Beyond that, there's plotting and pacing.  Mood and characterization.  I don't think anybody knows how to do these things without seeing how its done by others.  In our day to day lives, we communicate verbally.  And while verbal storytelling has its place, it's not the same thing as the written word.  Nor is video, such as televisions and movies.  The techniques used in those forms are not the same as the ones that a writer can effectively use.

I shouldn't minimize the danger of homogenization, where you start to sound like exactly what you read.  It happens (though I think that creative writing classes are more homogenizing than reading).  The cure to that is to read widely.  Read recent stories and old.  Read different genres.  Read fiction and non-fiction.  Read books written in other languages (in those languages, if you can).

Review of The Bard's Tale

I'm old enough to have played the original 1985 Bard's Tale game shortly after it came out, in glorious 320x240 4-color CGA. That may not seem like much to you kids, with your 1920x1080 16.7 million color 3D accelerated graphics, but it was a vast improvement over Bard's Tale's predecessors, such as the two color Wizardry. Like Wizardry, Bard's Tale was 3D, in that it involved exploring a dungeon in first person, with ten foot steps (none of that smooth, continuous movement of modern, or even old-school, first person shooters). Combat was text based, with you selecting each character's actions each round, but the real test was the exploration, mapping out each square of the dungeon on graph paper as you identified every trick, trap, and puzzle. And there were a lot, such as teleporters and spinners and areas of complete darkness--all intended to make mapping the area as difficult as possible.  I played through the first two games, but never made it through the third.

Well, like all things 80s, Bard's Tale is back. There's a 2004 remake sequel spiritual successor--well, a game by the same name anyway. It also has one of the same designers, Brian Fargo. Apparently, inXile Games, the designer, wasn't able to get the rights for the original game from Interplay, but they were able to, uh, borrow the name. Aside from the name, and some subtle references, there's not much similarity in story or gameplay. Which I guess is a good thing, as today's kids don't have the patience for the careful mapping it takes to play the original. Instead the new game is an action RPG in the vein of Diablo, but with less resource management.

I didn't get around to playing this new Bard's Tale until the last week or so, when I bought the recently released Kindle version for $3. After having played through it, I can say that it was well worth the time.

The protagonist and sole PC, the Bard, is not exactly a paragon of virtue. He's solely interested in coin and women, so it's curious that the imprisoned princess Caleigh has chosen him as her champion, and offered him the requisite price for his services (hint: it's not just money). Of course, Caleigh isn't picky. She's named dozens of Chosen Ones, mostly untrained farmboys, and the Bard is constantly tripping over their corpses. Fortunately, he's both more canny and more skilled than the aforementioned farmboys. Though perhaps not canny enough. He wanders around, solving almost as many problems as he causes, with the help of his summoned allies, his loyal dog, and a narrator who despises him.

The gameplay is straightforward and simple. You summon allies with your music, starting with a rat and progressing to tunes to summon knights and assassins. You can also cast spells with your limited selection of adder stones. But mostly, you whack things with your sword or shoot them with your bow. There are three levels of martial techniques for each weapon type, starting with basic competence and moving to more advanced types, all of which you can execute using just the attack and block buttons. I preferred dual weapon, with sword and dirk, but you can select weapon and shield, bow, two-handed sword, or flail. I never found the flail all that useful (while it can't be blocked, it takes too long to spin up), but some of the best weapons in the game are two-handers, and the bow makes certain fights much easier. As I mentioned earlier, Bard's Tale has simplified resource management. There are no trade-offs within a weapon type, so when you pick up a new weapon you'll either automatically equip it and convert your current weapon to silver, or convert the new find to silver, depending on which weapon is better. And while you can pick up a variety of junk, from pants to snow globes to self-help books, usually you convert them straight to silver.  Like most games, conversations usually have options, but your choices are always nice or snarky, and usually the nice is pretty snarky too.

I can go on about the gameplay and the story, but ultimately this game lives or dies by its humor.  The game is constantly poking fun at the tropes of computer role playing games, such as the cliched rats-in-the-cellar quest (it's a giant fire breathing one) and the wild animals dropping swords and silver (the narrator refuses to read those parts).  You'd also think it was a Rodgers and Hammerstein production, given the number of times drunks and monsters unaccountably break out into song and dance.  It's clear that this is a game that doesn't take itself too seriously, as you can see from the trailer:



So clearly, if you want to relive the original Bard's Tale games, you won't find it in this game.  But you should probably buy it anyway, as it comes with all three of the original games run in an emulator.  So you get the original games, and a very funny action RPG, which is a pretty good investment for $3, the going price for the Kindle version on Amazon.

You can buy the iOS version for $1.99, or find it for PCs on Steam for $9.99, which is pricey, but it's probably a better platform for the original Bard's Tale games.

Review of Ice Will Reveal by Julia Dvorin

Last October, my wife and I went to World Fantasy in Toronto.  One of the things you receive at World Fantasy is a huge bag full of free (in the sense of being included with the membership fee) books.  This year, the books included a number of cards which allowed you to download free e-books.  For the most part, I have yet to read the World Fantasy books, with the exception of Julia Dvorin's Ice Will Reveal.  This is not a coincidence.  Julia Dvorin's novel was the only e-book I downloaded from the World Fantasy book bag, since it was the only one that really grabbed my attention.  And I'm far more likely to read an e-book than a paper book.  It makes sense, really.  I have my smartphone with me at all times, and if I have some free time and nothing better to do, I can browse through my book collection and pick out something to read.  Whereas for paper books, I have to be at home in order to pick out a new book, and I can only carry one or two with me at a time.

Of course, the reason I selected Ice Will Reveal to download is because it was an unabashedly epic fantasy novel, which looked like it would be a fun read.  It was. It's about two orphans, a brother and a sister, named Jarrod and Whisper.  Jarrod is a Temple Guardsman, while Whisper is an apprentice acquirer of rarities.  In this story, that corresponds closer to thief than to adventurer, although her mistress, Mins, is certainly a high-end thief and fence.  Mins lives like minor nobility.

Jarrod is sent with companions to find a breach in the Boundary that holds back the Blight, the dead zone to the north. Jarrod already suspects that part of the reason he is being sent is as a test to see if he is indeed the Foretold, the one whom prophecy says is to repair the Blight.  He's not the only candidate for that position.  Yonenn, a Reaper Priestess, part of an order that worships the goddess in her death aspect, is also a candidate.  The prophecy says that ice will reveal who the Foretold is, so this trip to the edge of the frozen Blight is expected to resolve the prophecy. What they find is not the answer to the prophecy, and not only a breach in the boundary.  Something evil has started to come through.

Meanwhile, Whisper is sent to retrieve an important artifact necessary to repair the breach. Her quest involves significantly more grift and theft than Jarrod's, as the artifact is held by a creepy, but easily seduced, wizard, and it's up to Whisper to relieve him of it.

Things pick up once the two siblings return to the city, having found the breach and the artifact needed to seal it.  It was only a matter of time before Whisper and Jarrod joined forces.  They head out to repair the breach, and are doubly, or perhaps triply, betrayed by their companions, and then they escape and come back. And that's it, which is something of a problem.

While I thought the set up worked well in the novel, it fell short at the resolution.  We don't know whether the breach was repaired, as the one who was supposed to do it ran off with the artifact and disappeared.  We don't know what's going on with the quest to recover the Cauldron, the other artifact that's supposed to heal the Blight entirely, as the one who was supposed to do that also disappeared. We don't even know who the Foretold is for certain, although the clues point to Whisper, who wasn't even one of the candidates. In the end, the quest falls apart and the heroes go home.  Now as this is the first book of a series, I'm willing to cut the author some slack, and assume that these questions will be resolved in the next book. But I would have liked some better resolution, or at least a more satisfying climax, for this novel.

Copy

A friend of mine, and a contributor to the now defunct Storyblogging Carnival, is running a Kickstarter campaign to raise money for a television pilot.  Here's the plug:

COPY is a TV show about the student media at an evangelical Christian college: An editor trying to whip his staff into shape, a blogger more TMZ than T.S. Eliot, and a university president obsessed with being “culturally relevant” - negative press be damned. How far will editor-in-chief Meshach Kilbourne and his staff go to secure the paper's independence - and glory - against the machinations of President Constantine Ward?

It's an embellished memoir of our college years. And the pilot script for COPY - which, for reasons beyond us, has been called "Sorkinesque" - reached the semifinals of the Scriptapalooza competition last year.

If you're interested, consider pledging.

Latest Black Gate Review

My latest review is up at Black Gate.  This month, it's Robert Sier's Chains of Loss, but I've been calling it Cyborgs vs. Orcs.

Annoying browser tricks

From Instapundit:

THE BROWSER UPGRADE I’D LIKE TO SEE: One where the tab that’s the source of the autoplay audio flashes or something so I know which one to shut down.

To  which I'd like to add a hearty Amen.  When I open a whole list of bookmarks in tabs, and one of them starts playing an annoying advertisement, I have no alternative but to hit the mute button as fast as humanly possible.  I'd like to avoid that.  Some alternatives:

1. Mute all tabs except the one in the foreground. While simple and direct, there are situations where you might want to listen to sound in a background tab.  While listening to music from a browser-enabled cloud player.
2. Mute a tab until a user interacts with it. This would allow a tab to start playing music, but only after you click on it.  Of course, this would be annoying with YouTube's autoplay videos, but I find those annoying anyway.

What is love?

On a writers' forum that I participate in, the question was asked about how to motivate a character to stick with his first love once he becomes famous and successful, and suddenly finds himself surrounded by willing women.  I found this something of an odd question.  True, in real life, many men abandon their first wives once success gives them more opportunities, but I never would have thought it difficult to figure out a motivation to stay.

I've been married for two years, which is not much in the scheme of things, but I can say with some certainty that the reasons I love my wife don't go away the moment another opportunity comes along. So often what we love about someone is in the small things, the quiet moments when nothing is demanded and we can just be together, and it doesn't matter how rich one is or how successful someone's become. How much do they trust one another? How willing are they to share their secret fears and dreams and doubts without worrying about being judged? What inside jokes do they share? How well do they know each other's failures and weaknesses, and accept one another anyway? What do they talk about when they lie in bed together at night, just talking? How do they argue and make-up, and either compromise or agree to disagree? How do they show support for each other, when no one else in the world does? How do they sacrifice for each other, giving up what they want for what the other needs? How do they make each other feel needed and essential? What beliefs do they share, about what's important and what's not and what's right and what's wrong? These are the things that love is made of.

And though it happens a thousand times a day, you would have to be crazy to give up all that to be with someone beautiful but selfish, duplicitous, and shallow.

Which is pretty much what I said in the thread (though it was more directed to the specific question).

Boskone

Kristin and I went to Boskone this weekend, one of the science fiction conventions local to Boston.  It's not as literary as Readercon, or as costume and media centered as Arisia.  However, it is a lot of fun, as it has a good mix of panels, demos (including a lot of sword play), and an art show.  I only ended up going to two panels.  One for Military in Fantasy, and another for Advanced Writing Advice.  The first one wasn't as useful as I had hoped.  I wanted to hear about common military mistakes in fantasy, but they were pretty focused on avoiding deus ex machina, and didn't cover as much other ground as I had hoped.  The Advanced Writing Advice did offer some useful advice, but I don't think there was anything I hadn't heard before.

We went out to dinner with the Brotherhood Without Banners, a fan group for George R.R. Martin's A Song of Fire and Ice, on Saturday night, and by the time we got back the parties were winding down, so we hung out with the BWB and George Martin himself instead.  I also ran into John Murphy at Boskone, who I know through the Codex Writers' Group, though we didn't have much chance to talk.

Kristin will probably have a much more detailed con report,  but it may be a little while before she finishes it.

Ninth blogiversary

Today marks the ninth anniversary  this blog. I  know, it's Valentine's day.  Why did  I start a blog on Valentine's day?  Well, at the time I had nothing better to do.  Being a married man now, that's no longer the case.  Still, nine years is a long time. Hopefully it'll be around for another nine years.

Review of Throne of Bones by Vox Day

Throne of Bones is the first book in Vox Day's Arts of Dark and Light series. It is not the first story in this world, however, and Vox Day has previously written Summa Elvetica (under the name Theodore Beale) and A Magic Broken (which I've previously reviewed at Black Gate). The latest book, more than the first two, centers around Amorr,  a city where the Roman Republic meets the Catholic Church in a world of elves, dwarves, and magic.

I really enjoyed this book, but it needed better copy editing.  There were misspellings and misnumberings (particularly egregious when you identify legions by their numbers), homonyms mixed up, timeline errors, and I lost count of the number of times that the quotation marks were out of place.  None of these things are uncommon mistakes for writers--I make a lot of them myself--but that's why we have copy editors to catch them.  Some are bound to slip by, and I often see them in published books, but rarely this many.  Then there are the editorial decisions that I disagreed with but couldn't tell whether they were intentional.  Chapters from different points of view were out of chronological order, so a character who was dead in one chapter was alive again in the next one, only to die immediately.  Writers and editors sometimes do that sort of thing intentionally, and sometimes it's very effective, but other times it's just annoying (though still not as annoying as it was in Robert Jordan's Towers of Midnight, where Tam al'Thor was in two places at once).  Nor do I really enjoy the George R.R. Martin technique of apparently killing off a character, then having him reappear later without explanation, leaving us to guess at what happened, so I'm annoyed that I still don't know how Lodi and Thorvald escaped the dragon.

Now that I've got the gripes out of the way, what did I like about this book?  A lot.  I loved the use of Roman culture, although the prolific use of Latin to refer to everyday things may pose a challenge to anyone less familiar with Roman daily life than I am.  I like the fact that religion played a prominent role which was mostly positive but also corruptible.  I personally like dwarves, so it was good to see Lodi (an old friend from Summa Elvetica and A Magic Broken) as an important point of view character.  I thought all the characters were great, from noble Corvus to honest Marcus to self-absorbed Severa (who grows a lot in the course of the story). I liked the fact that the Amorran conflict is between two sides which have legitimate interests, both of which will use underhanded tactics to achieve them.  It was refreshing to see the good guys (to the extent that there were good guys) get fed up with the enemy mastermind's betrayals and killings and turn to the simple expedient of assassination.  Where honorable doesn't necessarily mean stupid.

So, for the most part, I forgive the novel for its mistakes.  However, I do hope that the next book has better editing.  And I wouldn't mind a corrected edition to the first book, either.

Local 623

My most recent story, "Local 623," is out at Nature Futures. Now all members of the Fraternal Order of Mad Science Assistants, Test Subjects, and Abominations can know their rights.

More of my writings can be found on the Writings page.

New Review at Black Gate

I've posted another review of a self-published book at Black Gate, this time of Noggle Stones: The Goblin's Apprentice by Wil Radcliffe.  I really liked this book, and I hope that my review will introduce more readers to it.  It's not without it's flaws, but then no book is.

New story out

Daily Science Fiction published my flash story, "Draconic Motivation," a week ago in their e-mail list.  It came out on their website earlier today.  It's a silly little story, but I liked it, and apparently I wasn't the only one.  Read it here.

New stuff, a lot of work

I managed to acquire quite a bit of new stuff in the past couple of weeks.  So much so, that it's been keeping me from getting work done.

One of those items is a Kindle Fire HD.  I knew I wanted one as soon as it had been announced, as it fixed many of the annoying things about the original.  I received a couple of Amazon Gift Cards for Christmas, and this seemed the perfect use for them. My first impression of the new Fire was that it was sleeker than the old one.  I got the 32 GB 7" version, since I liked the 7" form factor of the original Kindle Fire.  But in comparison to the new one, the old Fire is clunky and boxy.  I'll do a more thorough review later, once I peel myself away from Final Fantasy III for the Kindle long enough to experiment with some of its other capabilities.  Now I just need to figure out what to do with my old Kindle Fire.

The other thing that arrived this week is a desk.  I ordered the Versa Center from VersaTables and spent some time this week putting it together.  I got this desk because I was buying a desk treadmill from Lifespan, and needed a standing desk to use with it.  The Versa Center isn't really a standing desk, but each and every shelf is adjustable to any height, so I was able to make it into a standing desk.

Treadmill and Versa  Center

From the treadmill, I have a good view of the television in my living room, which is hooked up to one of my computers (the one I mostly use for gaming).

The view of the television, and my wireless keyboard.

I really liked the Versa Center's flexibility, but I'm reluctant to recommend it to others.  There are no fixed mount points--all the shelves clamp onto the poles on either side of the desk, and it took two people, a measuring tape, and a level to get the two sides of each shelf lined up. Nor was there any indication of the angle that the components clamp on, so getting them parallel was an iterative process of  eyeballing it, bolting in the shelves and support bars, and then adjusting so you could get the other side bolted in. And even then, I don't think the tolerances were quite right--I still wasn't able to line it up well enough to get all the screws in.  But I think I'm at the point where it's good enough for now.  I can now walk on the treadmill while writing this post on my laptop (I suppose I could use the computer connected to the television, but that's for games).     I haven't quite decided whether I'm comfortable with the distance, or whether it's worth going through the expense and trouble of installing a keyboard arm.

I like having a treadmill desk, but I still miss by old treadmill.  I got rid of it when I moved into my previous apartment.  The old treadmill was significantly bigger, and wouldn't have worked with a desk anyway, as its lowest speed was 2.5 mph, which is too fast to comfortably write.  Right now I'm walking at 1.2 mph, which works for me, and I may pick up the pace a bit more, but I doubt I can comfortably type above 2 mph, and certainly not while running.  But at least I could run on my old treadmill.  The new one only goes up to 4 mph, which is just a light jog.

My old treadmill.

Review of A Memory of Light by Robert Jordan and Brandon Sanderson

I was going to write a long review of the final book of the Wheel of Time.  But, really, I'm not sure that much more needs to be said.  The Wheel of Time has been an important mainstay of epic fantasy for over 20 years.  Begun by Robert Jordan with the publication of The Eye of the World, after his death it was completed by Brandon Sanderson with the last three novels: The Gathering Storm, The Towers of Midnight, and A Memory of Light.  At least portions of the final novel were written by Robert Jordan before his death, though I won't hazard a guess as to which portions.  The Wheel of Time has had ups and downs.  I personally didn't get into it until the third book, The Dragon Reborn, and there were certainly books along the way that were significantly below par.  Some of the novels around books seven to nine  seemed to contain no significant plot developments, and the whole book seemed to be spent catching up with each character, reminding you of what they were up to, and then switching to the next.  But then things began to pick up just before Robert Jordan died, and Brandon Sanderson was able to bring it to a conclusion.

The whole final book centers around Tarmon Gaidon, the Last Battle.  It's actually about a series of battles, on numerous fronts.  And if you find battle scenes boring, then you're going to have difficulty with this one.  There's one 200 page chapter about a single battle.  It is the main one, and deserves a lot of attention, but still, that's a long time to spend on a single battle. Rand al'Thor, the main character, has what is actually a pretty minimal part on this front.  He's too focused on his own struggle with the Dark One, which is a lot more personal and focused--practically a duel, though one fought with ideas and the threads of reality, not swords or magic.  But many of the major characters, and most of the minor ones, are involved in the battle, including Lan, Elayne, Egwene, Suiane, Gareth, Tuon, Gawyn, Galad, Faile, Olver, and especially Mat, in the role we always knew he would have.  Now, I've said before that Brandon Sanderson doesn't really seem to get Mat, and that shows up in the early parts of the novel, but in the Last Battle he seems to be in fine form, showing the sort of mad brilliance we expect from him when it comes to war.

I won't say the battle dragged, because it kept me up all night trying to finish it, but there were moments where I wished Brandon would pick up the pace.  On the bright side, everybody had a role and a chance to shine in this book.  They needed to.  On the other hand, not everyone's role was what I might have wished.  Perrin managed to miss the big battle in the south, and only showed up for the showdown in the North, a smaller but equally important battle.

One of the requirements of the final book in a series is to fulfill all the promises given in the previous ones.  As there were a lot of prophecies, that was a lot to fulfill, and not all of them were met in a very satisfying way.  Suiane's and Gareth Bryne's, for example.  Or Alivia's.  In some places it felt like shortcuts were taken to get the prophecy resolved, but I suppose that was inevitable, given the scope of this vast series, and exactly how many promises there were to fulfill.

But ultimately, I was satisfied with the ending.  Not everyone survived, and in some cases I was surprised by who did and who didn't, but that was satisfying in its own way.  And the last chapter contained a couple of final surprises that I think were worth waiting for.

Redundancy Checker update

A week ago, I discussed my travails in getting my Java program working.

After some hunting, I've found an improved version of the RTFEditorKit at this site--an AdvancedRTFEditorKit. It's still not perfect, and it still loses smart quotes, but it does allow you to subclass its classes, which is something the old RTFEditorKit did not allow. You could subclass the kit itself, but not any of the classes it used to do the real work, which is what I needed. By subclassing the new RTFReader, I may be able to do some preprocessing and post processing in order to deal with the idiosyncrasies that are showing up. Unfortunately, some experimenting showed that my original idea (replacing \'93 with \ldblquote) won't work, though I suppose I could replace it with straight quotes.

It's all very annoying.  The whole idea of object oriented programming is that I wouldn't have to write an RTF reader from scratch.  I'm beginning to wonder just how much time I'm willing to dedicate to this.