Martin Wisse, Author at Martin's Booklog

1983: The World at the Brink — Taylor Downing

Published on May 26, 2023Leave a comment

Cover of 1983

1983: The World at the Brink
Taylor Downing
391 pages including notes and index
published in 2018

If there ever was a movie that embodied the fears about nuclear war I had living through the early eighties, just old enough to understand the concept, it has to be Threads. I turned nine that year, just old enough to start to comprehend what nuclear war would be like. We had an insane cowboy in the White House who talked about a winneable nuclear war and a series of rapidly decomposing, extremely paranoid leaders in the Kremlin. One small mistake and the world would’ve ended. And while I didn’t learn about Threads long after the cold War had ended, I really didn’t need it to have nightmares. Any mention of anything nuclear on the news was enough to set them off. It didn’t help either that pop culture at that point was saturated with nuclear war imagery.

Fortunately, Threads was never broadcast in the Netherlands at that time, or I would’ve never been able to sleep ever again. Learning about it in a BBC retrospective somewhere around the turn of the millennium was traumatising enough already for the nightmares to return. That shot of the mushroom cloud going up over Sheffield with the old lady in the foreground pissing herself. That was the sort of fear and anxiety, that feeling of helplessness I grew up with in the eighties, in a country where you couldn’t pretend that you could have cool adventures fighting mutants afterwards. No, you either be dead or wishing you were. Being a sensitive kid I didn’t need to see nuclear war movies to imagine how horrible it would be. Which is why I won’t be celebrating Threads day by finally watching it.

Threads: Thursday May 26th 08:00

No, I prefer to feed my nightmares through print, like with Nigel Calder’s Nuclear Nightmares which I reread a couple of years ago. As with so many people my age I know, I can’t help but occasionally pick at that scab. Especially as I got older and learned more about the realities behind my nightmares, I can’t help but want to learn more about it, to confirm my fears weren’t unfounded. 1983: The World at the Brink is very good at doing exactly that. It not only confirmed that my childhood nuclear war paranoia was justified, it showed things were so much worse than I could’ve ever imagined back then. 1983 may very well have been the most dangerous year of the entire Cold War.

The way Taylor Downing sets about showing why this is the case is by providing a chronological overview of the year and its crisises, until about two-thirds into the book we hit the ultimate crisis point, the moment civilisation could’ve ended if things had gone even slightly differently. He starts with a short explanation of the context in which these incidents took place. How the detente of the seventies had ended with the Soviet invasion of Afghanistan in 1979 and the election of Ronald Reagan, gun-ho to take on the Evil Empire, in 1980. That with the death of Brezhnev in 1982, the head of the KGB, Andropov would be made the leader of the USSR,a man made paranoid by the Hungarian uprising of 1956, which he played a role in suppressing. Here there was a leader of the Free West who started talking about a winnable nuclear war opposite a Soviet leader deadly paranoid about attacks on his ‘socialist paradise’. Not a good combination in a time when tensions were already rising due to Afghanistan.

In 1981, while still head of the KGB, Andropov had already launched Operation RYAN, an intelligence programme aimed at determining whether the US and NATO were preparing for a nuclear first strike. By 1983 this operation was intensified as the US was starting to deploy cruise missile and Pershing II nuclear missiles to Europe as part of Reagan’s general re-armament plans. While RYAN was intended as a safety measure, its real effect was to feed Andropov’s paranoia, making him increasingly concerned that the US was planning a first strike. Reagan meanwhile, cheerfully unaware of this, was talking up plans to create a missile defence system against nuclear attacks, making America invulnerable. Regardless of the technical merits of Star Wars, even thinking about such a defence against nuclear attack was threatening the status quo of mutually assured destruction. Peace was being maintained because both sides could destroy the other completely, regardless of who shot first. There was no advantage in starting a nuclear war as long as everybody died in it. But if an increasing technological advance meant the US could defend itself, or could unleash such a devastating first strike that retaliation was impossible, that put the USSR in a dilemma. If the US was preparing a strike, the Soviets should strike immediately before the strike had even launched, or risk being caught off guard. And that was much more ripe for error than if you wait until the missiles have actually launched.

And then, in September 1983, a Korean airliner blundered into Soviet airspace, was mistaken for an American military spy plane and through a series of tragic errors, shut down with all passengers and crew killed. That immediately shut down any tentative prospect of unfreezing the Cold War. It strengthened Reagan’s opinion about the USSR being an evil empire, while it also fed Andropov’s paranoia about the country’s vulnerabilities, that an airliner had been allowed to enter sensitive airspace unchallenged. All this set the stage for Able Archer, a NATO military exercise, which simulated a Soviet invasion of West Germany culminating in a NATO nuclear strike to stop the advance. A so-called command post exercise, in which the various military headquarters were involved but not so much soldiers out in the field, the USSR was convinced it would be cover for a real first strike against it. It had take measures to reduce its vulnerability, by putting its nuclear forces on high alert, by making the preparations for a strike so that if it was necessary it could be done almost immediately. All that was needed was for Andropov to become convinced America was about to strike and give the order to strike first. And the moment that would happen came increasingly close as the NATO exercise grew in intensity.

At this point in the book Downing had thrown me deep into that paranoid mindset; my relief when the crisis passed was palpable, even knowing full well nuclear war hadn’t happened in November 1983. The rest of 1983: The World at the Brink is more cheerful, describing how both leaders walk themselves back from the abyss. How with the deaths of first Andropov and then his successor Chernenko the way was freed up for Gorbachev, a true reformer who managed to build a personal bond with Reagan, who set in motion the events that would lead to the end of the Cold War as well as the Soviet Union. Even more than three decades onwards, it’s still a miracle such a vast and powerful empire could be dissolved mostly peacefully, that we didn’t all die in nuclear shock waves in November 1983.

If you’re my generation, this book then is the confirmation of all the old bad dreams you had back then. If you’re too young to have lived through it yourself, a good look back a period where all this was normal.

A Night in the Lonesome October — Roger Zelazny

Published on November 2, 2022Leave a comment

Cover of A Night in the Lonesome October

A Night in the Lonesome October
Roger Zelazny
Gahan Wilson (illustrator)
280 pages
published in 1993

A Night in the Lonesome October is a special book: except for the various collaborations he did with Robert Sheckley and others, it was the last novel written by Roger Zelazny before his death two years later. It was also a return to form. Zelazny had been one of the more interesting writers to emerge from American New Wave science fiction back in the sixties and had been a steady Hugo and Nebula nominee and winner in the sixties and seventies. the latter half of the eighties he had been mostly concerned with writing the second, lesser Amber cycle while in the nineties he mostly collaborated with other writers. A Night in the Lonesome October was the first new, solo non-Amber Zelazny novel since 1987 and more than that, it was good. As such it became a bit of a fan favourite among the people on the Usenet group rec.arts.sf.written, which resulted in a tradition of reading the novel day by day during October each year. This is possible because each chapter is a diary entry devoted to one day in October. I never took part in this, but this year I decided to try it when I wanted to reread it. (UPDATE: liar.)

Set in Late Victorian London, A Night in the Lonesome October is the diary of a dog named Snuff, companion to a man called Jack who has a special knife. Yes, that Jack. He and Snuff are participants in the Game, held every few decades when there’s a full Moon on Halloween, October 31. There are some other, very recognisable characters taking part in this game: a certain Count, the Great Detective (of course), the Good Doctor and his self made man, etc. There are also some less recognisable people taking part in the game, like Crazy Jill and her cat, Graymalk, the latter as close to a friend that Snuff has in the Game. What the Game is about is only gradually made clear, but it is one played between two sides, Openers and Closers. Each player may not know which side the others are on; each player is basically playing on his own until the climax. Therefore there’s room for schemes to be drawn up, alliances to be made and betrayals to happen.

It takes discpline to read A Night in the Lonesome October this way, day by day, especially at the start when the chapters are sort. The tendency to read ahead is great because Zelazny sprinkles enough interesting tidbits around even in these short chapters to tempt you into reading further. Why is a dog keeping a diary and why is it Jack the Ripper’s dog? What are the Things it is guarding in the Mirrors, Circle, Wardrobe and Steamer Trunk? What is it patrolling for and what is it his master is seeking? What does it all mean? Luckily ultimately every question does get answered, albeit often indirectly and in passing. The backstory is only hinted at, never explained. There’s also a little bit of legerdemain going on; not every player is what they seem, nor is every player even in the game. Not everything that looms large in Snuff consciousness as part of his duties is as important as it seems either, especially in those early chapters.

A Night in the Lonesome October at heart is a horror mystery pastiche where a lot of the fun comes from that frisson of recognition as characters wander in and out of the story and understanding their true roles in it. It’s a fun little book that you’d normally read in an hour or two, but reading it spread out like this heightens the anticipation for each chapter. I’m not a patient man and it did take some effort to stick to it, but I’m happy I did. Even if the whole book seems to have written for the truly awful pun in the second to last line of the story…

Hutu en Tutsi: Eeuwen Strijd — Peter Verlinden

Published on July 17, 2022Leave a comment

Cover of Hutu en Tutsi: Eeuwen Strijd

Hutu en Tutsi: Eeuwen Strijd
Peter Verlinden
177 pages
published in 1995

Published in 1995 after the Rwandan genocide had just ended, Hutu en Tutsi: Eeuwen Strijd tries to explain the context and history in which it took place. The writer, Peter Verlinden is a Belgian journalist who had been covering events in both Rwanda and neighbouring Burundi for several years before. This is not a book about the genocide itself, which is only briefly touched upon in the last few chapters, but an explainer of what made it possible. With only 177 pages to cover the whole history of Rwanda it’s of necessity more of a sketch than a complete picture. As the title Hutu en Tutsi: Eeuwen Strijd (Hutu and Tutsi: Centuries of Conflict) indicates Verlinden argues that the genocide was only the latest in a long line of conflicts between the two ethnic groups and should be seen as such, not as some inexplicable outburst of violence. The genocide, together with what was happening at the same time in former Yugoslavia was what broke the short lived optimism brought on by the end of the Cold War. The idea that now the civilised world (sic) would be able to intervene in conflicts and resolve them was proven wrong by the inability or unwillingness of the UN to stop the genocide as it was happening.

By focusing on the supposed long standing history of ethnic violence in Rwanda you might read this as an excuse for the failure of Belgium and other interested nations to stop the genocide. We saw that line of thinking trotted out a lot during the early years of the Yugoslav civil wars, the idea that Serbs and Croats and Bosniaks just naturally hate each other which you couldn’t do anything about. I was a bit wary of this myself when I first read this, but on the whole I think Verlinden did a good job explaining the circumstances and history driving the genocide without excusing it. Verlinden lets the facts speak for themselves and it’s up to the reader to draw the conclusions and lament the missed opportunities to stop the genocide.

After setting out what the book is about, Verlinden starts with a short history of pre-colonial Rwandaand its first inhabitants, the Twa. These were forest dwellers until the Hutu appeared, some 200-3000 years ago, who brought agriculture with them. The Tutsi arrived later and were pastoralist herders. To say that the Tutsi conquered Rwanda from the Hutu would be wrong, but over the centuries their power did grow, conquering the various Hutu kingdoms. By the nineteenth century it was Tutsi king who ruled most of Rwanda and a Tutsi elite that shared that power, while the Hutu majority were mostly small farmers. A roughyl feudal society, with the Hutu farmers obliged to service their Tutsi masters in various ways through unpaid labour and taxes in kind. At the same time, there were no hard ethnic borders between Hutu and Tutsi. Hutu could become part of the elite even if that was rare and whether you were either depended as much perhaps on your social status as your ethnicity.

As per usual it was the colonisers that fucked things up. First the Germans, then the Belgians took that existing divide between Tutsi and Hutu and codified it as strict ethnicity. For various bullshit racist reasons the Tutsi were elevated as closest to being white and therefore natural leaders, which meant that they got most of the positions of power in government, church and trade. The Belgians especially favoured the Tutsi at first. It was only post-war, in the fifties that this stopped as new generations of Belgian colonial administrators and church officials started instead to take the impoverished Hutu’s side. Belgium never ruled Rwanda directly, but through the existing Tutsi kings, the same way the Germans had done. By now supporting a new generation of Hutu activists and intellectuals demanding a greater share of power, they of course threatened the monarchy and its power structures. Matters came to a head as Rwanda prepared for independence.

An attack on a Hutu politician led to mass attacks on Tutsi leaders and others. The kingdom collapsed, a republic was declared and hundred thousands of Tutsi fled abroad. In Rwanda itself Hutu took over much of Tutsi power and the republic lasted until 1973 when a coup deposed the government and the second republic was proclaimed. Throughout this there were low level tensions between the two groups and occassional outburst of violence, but the real trouble started in 1990, when Tutsi refugees invaded the country to liberate it. That led to several years of civil war and more mass violence against both Tutsi and Hutu, until a peace treaty was signed in early 1994. Everything seemed to be calming down again until the president was killed in an attack on his plane coming back from the peace conference. That was the point at which the genocide started, as at first the Tutsi rebels and sympathetic Tutsi leaders were targeted but quickly escalated to include all Tutsi or ‘Tutsi looking’ people were attacked, as well as moderate Hutu.

Hutu en Tutsi: Eeuwen Strijd concludes at this point. At the time of writing Rwanda was still in an uneasy peace, with Tutsi refugees from that first wave of violence at the establishment of the Rwandan Republic returning home after decades, while million others, mostly Hutu had now fled abroad. Many of the Rwandan Tutsi had died in the genocide and their place was taken over by the returnees, who became the new elite. You can see the fires for the next conflict already being stoked while the embers of this one were still glowing, the way Verlinden describes it. In the almost three decades that have been passed since a new genocide fortunately hasn’t happened, but the conflict ia still ongoing, with Hutu refugees in Burundi and the DRC continuing low level guerilla campaigns, while Rwande has intervened in the Congolean civil wars twice as well.

I first read this in 2002 when I got it as an ex-library book and reread it today purely because my eye fell on it. This was a decent primer on the context of the genocide, but these days you might as well read the Wikipedia articles on Rwanda and its history. that of course wasn’t an option in 1995 and barely one in 2002, so I’m grateful to Verlinden for this.

American Tanks & AFVs of World War II — Michael Green

Published on April 30, 2022Leave a comment

Cover of American Tanks & AFVs of World War II

American Tanks & AFVs of World War II
Michael Green
376 pages including notes & index
published in 2014

It’s a fact of life that interest in World War II armour tends to focus on Nazi Germany, with Soviet vehicles perhaps a distant second. Understandable, considering how many interesting and downright strange types made it into production or had at least a prototype created. It’s always tempting to think about what if those potential wunderwaffen had made it into service, whereas the realities of western allied armour are always much more mundane. At least the French and to a lesser extend, the British, had some cool but impractical dead ends available in the early war, but American armour was just relentlessly pragmatic. the answer to any problem encountered seemed to be let’s build more Shermans, rather than creating some new exotic prototype.

American Tanks & AFVs of World War II does nothing to disabuse you of those preconceptions. Yes, there are some what ifs to be found, but in case after case what Michael Green documents here is the ruthless pragmaticism of the US army during world War II. It’s not just that the whole design and procurement process was much more centralised and efficient than that of Nazi Germany — but it certainly helped that there was no Hitler type mucking about on the US side. It’s also that the first instinct was always to look for solutions through modifying existing vehicles, rather than creating new ones. A determination not to let the perfect be the enemy of the good or even good enough. If it worked, why replace it just because there was a better option? That’s the attitude that comes across reading this book.

After a short introduction, American Tanks & AFVs of World War II starts with the development of medium tanks between the wars, culminating in the M3, the first major US tank of World War II, which saw action in North Africa and Italy, as well as the Pacific. This is followed by a long chapter on the development of the ultimate American medium tank, the M4 or Sherman. The Sherman as a tank had always been a bit confusing to me, because its long production and gradual evolution meant there were a confusing number of subvariants and it isn’t always easy to distinguish them. Therefore I appreciate Michael Green’s efforts here to make sense of them all. With the focus on World War II it’s not an entirely complete story of course, as there were numerous post-war variants as well. Not to mention British variants like the infamous Firefly.

The chapters on light and heavy tanks are together only slightly longer than the M4 chapter, which shows its importance. The heavy tank was never that much of a priority to the US army in the war; there never was an equivalent of the Tiger. The 75 or 76 mm armed Sherman was deemed good enough. When there was a demand for a more heavier armoured tank therefore, the Sherman was up-armoured rather than a new tank created. The only tank taken into service that could be classified as heavy would be the M26 Pershing, which only arrived very late in the war. On the light tank front, things were somewhat different. The M3 and M5 series were excellent scout vehicles much used by both the US and the British/Commonwealth, while the M24 was the ultimate WWII light tank, armed with a similar 75mm gun to the Sherman. Again it’s telling that the 37mm armed M3/M5s were kept in service for so long despite their main armament being obsolete almost from their introduction. Their role wasn’t to fight other tanks and the US was never tempted to upgun them just because they could.

Tank destroyers were an important part of US army doctrine, as they were intended to fight enemy tanks rather than leaving it to the tanks themselves. This used to be the tasks of towed anti-tank guns before the war, but the German blitzkrieg put paid to the notion that towed guns could suffice. The first generation of tank destroyers mated existing, often obsolete guns with wheeled vehicles or half tracks. There was e.g. the M3 half track with a World War I vintage 75mm gun that was used in North Africa and Sicily. With the limitations of this sort of design becoming obvious, the next step was to create tank destroyers from existing medium tanks. The M10, M18 and M36 all used the M4 chassis with new turrents and different guns: a 3 inch, 75mm and 90mm respectively as demands for more fire power increased.

The remaining chapters detail the more niche armoured vehicles used in World War II: armoured cars and half tracks, self propelled artillery and tracked landing vehicles. The ruthless pragmatism of the US army really shows through well in these first two categories, with only a very limited number of different armoured cars and half tracks ever taken into series production. The first especially, with only a few types of light armoured cars taken into service and no heavy ones, unlike other armies. With self propelled artillery, there was the same sort of trajectory as with tank destroyers: first using wheeled vehicles before moving on to using the M3 and M4 tank chassis. Tracked landing vehicles were of course mostly used in the Pacific, but also by some of the river crossings in North West Europe late in the war. Again, any improvement here was evolutionary rather than revolutionary, with heavier armament added as needed.

If you want a one shot overview of American tank and armoured vehicle development during World War II, this is an excellent introduction. Plenty of excellent photos and illustrations too help tell the story. Recommended.

The Key to the Bulge — Stephen M. Ruseicki

Published on April 24, 2022Leave a comment

Cover of Snow & Steel

The Key to the Bulge: The Battle for Losheimergraben
Stephen M. Ruseicki
195 pages including notes
published in 1996

A visit to the Bastogne War Museum when I was on a holiday in the Ardennes last October got me interested in the Battle of the Bulge again, as did the series WW2TV did on the campaign in December. Their interview with Peter Caddick-Adams on 10 Facts about the Battle of the Bulge everyone should know led me to read his excellent book on the campaign as a whole. Which in turn whet my appetite for more on the individual battles within the Ardennes Campaign. Military history like all history is fractal after all. You can get a broad overview but if you zoom in you get a lot more detail, new insights. Which is where this book comes in. With Snow and Steel I got the broad strokes of the Ardennes Campaign, with this I got an overview of one of the most important of the early battles in it, one that could be argued determined the outcome of the entire Ardennes Offensive…

That battle was the battle for Losheimergraben, then, as now, a small border crossing between Belgium and Germany, too small even to call a village. In December 1944 this was the front line, the furthest point reached by the great Allied breakout from Normandy earlier that year. Since then the front line in the Ardennes had been largely static; the real fighting continued further up north, in the Netherlands and around Aachen. The Ardennes itself was quiet, an ideal sector to introduces green troops to life at the front and blood them before they got thrown into real battle. Losheimergraben and neighbouring places like Lanzerath were held by such troops, the 394th Infantry Regiment of the 99th infantry Division. It was these troops that would hold out for thirty-six hours against the Sixth Panzer Army starting on the 16th of December, denying it the quick victory it needed to comply to its already impossible schedule.

Hitler’s original idea behind the Ardennes Offensive was to repeat the success of May 1940, when Germany’s panzers broke through the “impenetrable” Ardennes and split the Allied forces in two, ultimately sealing the fate of France and driving the British from the continent. This time his strategic aim was the same, but aimed at seizing Antwerp, denying the Allies its use and splitting up the British and American forces. There are however relatively few passages through these mountains that are usable by armour, of which the so-called Losheim Gap, also used in 1940, is one. Grabbing Losheimergraben, where an east-west road from Germany into Belgium intersects the main north-south road in the Ardennes, was to be the first step in the German drive through this gap. From there the goal was to drive the panzers forward into Bullingen, to Malmedy and beyond to cross the Meuse. Once the Meuse crossings had been made the panzer armies could drive onto Antwerp and victory. But it all depended on seizing those border crossings and seizing them quickly and that would be a job for the infantry.

The American defenses in this crucial sector, as they were all across the Ardennes, were light. Because it was regarded as a quiet sector, not only was it considered an excellent sector to bleed green troops in, it also meant fewer troops were stationed there in the first place. Which meant individual divisions had to defend larger pieces of the front line than was recommended. The 99th Infantry Division therefore had little in the way of reserves, needing all three of its regiments to remain in line to cover the entirety of what it was responsible for. Worse, it was stationed on the border with another army corps, with Lanzerath and the Losheim Gap right on the border, barely covered by any American soldiers. This is the stage on which those initial German attacks happened on the 16th of December. Yet despite being outnumbered and surprised, the inexperienced men of the 394th regiment of the 99th division held out for more than a day against the German onslaught. How was this possible?

As Ruseicki describes it, it’s clear the tenacity and sheer dogged will of these American soldiers to resist played a big role. they may have been green, but they were well trained, their morale was good and they weren’t going to just roll over. Making good use of their defences they held back the enemy as long as they could before withdrawing in good order to a new defensive line. Ultimately they were never broken and the Germans never quite managed to break through, the offensive stalled almost from the start. Looking at it from the German side, it’s clear that they had problems even had their opponents been a pushover. The obsession to keep the offensive a secret meant little preparation and with no reconnaissance allowed, they had no idea what they were walking into. Having soldiers that on the whole turned out to be just as green as the Americans, but far less well trained, didn’t help either. If reading this you are reminded of how Russia’s currently bungling its war on Ukraine, you’re not the only one…

This was an interesting look at one of the opening battles of the Ardennes Offensive. Ruseicki describes the action well without being overtly dramatic. A good example, well explained, of how small scale battles can impact a wider offensive.