Saturday, July 12, 2008

Countdown to Nowhere


(This is a follow-up post to yesterday's "Buzz Off" which concerns astronaut Buzz Aldrin's recent statements that shows like Star Trek led to the decline of support for the space program. If you haven't read it, go there first.)

I've gotten a lot of support and "attaboys" from people who read "Buzz Off," but it turns out I didn't win over everyone. Fact is, I thought this over pretty carefully, and there's a lot of stuff I DIDN'T put in the original post, because I didn't think it was necessary given the basic
facts. More would have just been clutter.

But since the facts weren't as obvious as I supposed, let's look at another major
problem with the Buzz Aldrin theory. I don't think the historical time-line supports it.

At first glance, though, you might think the dates line up well. Star Trek was on TV from September 1966 through September 1969. The collapse of the space program's support is really centered around 1970. (The live TV broadcast from Apollo 13 wasn't covered by any of the major networks live, and it flew in April 1970. Apollo 20 was canceled in January of 1970. Two more Apollo missions were canceled in September of 1970.)

So the dates seem close, but I don't think it holds up to scrutiny.

First of all, remember that Star Trek was a failure in its broadcast run. It was nearly canceled in September of 1968 (while Apollo 8 had the world's attention, and Apollo 11, which drove the country (and the world) into a frenzy was nine months away. In fact, the decision to pull the plug on Star Trek had to have been made just about the time Apollo 11 landed, and the program was at the peak of its popularity and public interest.

Star Trek REALLY didn't take off until it was in syndication and college kids started watching it. I don't have a good date for that, but I suspect we're talking 1971 or 1972, when the smoking gun had long-ago gone off.

But the decisions to pull the trigger on that gun had to be made earlier.

Congressional support had to deteriorate sometime well before the cuts started, and the decision not to cut-in live on Apollo 13 probably resulted from viewership numbers on Apollo 12, which flew in November of 1969.

Of course, Apollo 12 blew out its TV camera shortly after landing, and that probably accounts for a lot of any ratings tumble. You can hardly blame that on Star Trek. (Ironically, almost without exception, Star Trek never showed TV cameras being taken along by its explorers.)

In any case, if Star Trek somehow poisoned the U.S. public on the space program, it did it as a low-rated show with a limited audience. And indications are that, during both first-run and in its re-run "boom" period, the audience for Star Trek largely consisted of people under 21. The voting age was still 21 at this time, and wasn't lowered to 18 until July of 1971. So as far as political influence, it's hard to see how it ever could have had any significant impact at that point in time.

The first evidence that Star Trek fans had political clout didn't come until the first Space Shuttle was renamed ENTERPRISE, following a letter-writing campaign to the Ford White-house by fans. I don't have a date for this, but it happened sometime between when President Ford took office in 1974 and the Enterprise roll-out in 1976. Since construction didn't start until June of 1974, and its original name was "Constitution," and Ford took office in August of '74, it would not likely have been any earlier than that. It's very likely that the reduction in the voting age was a factor here.

Regardless of the date, this hardly supports any lack of support or interest in the real space program by Star Trek fans. Quite the contrary.

On the other hand, NASA's internal grumbling and foot-dragging on the matter is a fine example of how they loved to shoot their public image in the foot. Here was a great opportunity to connect their mission with the public, and rather than exploit it to the fullest, they minimized it as much as possible.

I just don't see any evidence here that Star Trek harmed the space program in any way.

Of course, Aldrin wasn't specific that he was talking about Star Trek, but there just aren't many other on-air TV candidates for killing support of the Space Program.

Lost in Space started (and ended) a year earlier than Star Trek, and had a much bigger audience than Star Trek, but there was no beaming there. There were aliens (often very silly aliens) and interstellar travel (though the science was so weak that I don't recall any kind of faster-than-light drive ever being mentioned). But most of the signature hardware, robots, space-walks, jet packs, surface crawlers, and a very LM-like landing vehicle, were all right off the NASA drawing boards at that time. It was more futuristic and advanced, but in its own way, much more realistic than Trek.

The British series UFO (which featured a modest and fairly believable lunar base) didn't reach U.S. syndication until 1971 and 72. The follow-up Space 1999 with a much bigger Moon base (and some screamingly bad science) didn't show up until 1975.

Other than that, I can't think of anything (other than some Saturday morning cartoons) that qualifies. Feel free to correct me if I've missed something significant.

Meanwhile, all the stuff that Aldrin frets about, teleportation, faster-than-light travel, and so on, had been popular staples of print and comic science fiction since at least the 1930s. Somehow, the U.S. space program got off the ground anyhow (mostly by people who had at
some point read plenty of the stuff.

And we can't ignore movies. Flash Gordon and Buck Rogers were rocketing off to alien worlds in theaters as early as 1936 (and on radio starting in 1932). Heck, even Duck Dodgers used a teleporter in his first 1953 cartoon appearance!

None of the offending concepts or devices was invented by Star Trek, or any TV show. It predates broadcast television entirely.

Really, looking at the evidence, if the time-line supports anything at all, it's the idea that cutbacks in the Apollo program (and news coverage of same) may have contributed to the renewed popularity of Star Trek in syndication in the early 70s.

If the real space program wasn't going to give us the stars (or even the Moon again, or Mars) anytime soon, we'd watch Star Trek and dream until it did.

That just makes more sense than the idea that B led to A.

But there's a subtext in the time-line the supports more significant factors.

At least some of the press (and the public's) interest in covering the Apollo program has to be traced to the camera failure on Apollo 12. Apollo 13 might have turned that around, but it never made it to the moon, and was covered for entirely different reasons.

Support for Apollo in congress was weakening by early 1970, when Apollo 20 was canceled. The next two cancellations happened after the near loss of Apollo 13. By then, the risks were obvious, and there's no political stock to be gained in backing a losing horse. Better to end the program a winner.

It was also obvious by then that the press was more interested in covering failures in space than successes. Lose, lose. Not much here you can blame on Star Trek.

Combine this with the growing cynicism about government, and the huge cost of the Vietnam war (which lead directly to the cancellation of the Air Force's manned space program before it even started), and there just wasn't anything to be gained politically by backing NASA. Again, not Star Trek's fault.

The facts aren't there. The logic isn't there. Star Trek didn't do it. No science-fiction TV show did. If anything, Star Trek has been a positive influence on people's interest in space.

So, anybody want to start a write-in campaign to name the first, manned, Orion crew-capsule to reach orbit (no test models this time!), Enterprise?

More writings about the Moon:

Closely related to this topic, I have a couple of previous posts about the Moon and the Apollo program that you should check out:

Buy Me The Moon
Why the Apollo program didn't cost nearly as much as most people think it did, and how we might trade certain -- luxuries -- for a Moon base or a Mars program.

1200 Days On Mars
People say there's no reason to return to the Moon. "Been there, done that, got the tee-shirt." Well, we haven't been there, haven't done that, and we don't even know where the tee-shirts are sold. How we've barely touched the Moon, and how it compares to our current unmanned explorations of Mars.

Friday, July 11, 2008

Buzz Off



Don't you hate it when one of your childhood heroes says something so profoundly wrong and stupid that you just have to call them on it? Unfortunately, it just happened to me.

The hero in question is Apollo 11 moon-walker Buzz Aldrin. Ironically, I ran across this story on the US Sci-Fi Channel's "Sci-Fi Wire" news site. If any of the space sites or major news sources picked it up, I didn't see it. Aldrin was shilling his new National Geographic Channel show, "Unseen Moon," at the annual TV Critics Press Tour.

Anyway, Aldrin went on about how "unrealistic" science fiction television shows caused the public to lose interest in the space program. He doesn't name names, but he keeps mentioning "beaming," which seems like a reference to Star Trek. But he also is quoted as saying something about the shows being on "today," which kinda points a finger towards Stargate Atlantis, the only other current show I can think of that "beams" people.

Or maybe he's confusing reruns with new shows, or is being unclear about the time. Because, the public started losing interest in the space program before half the people working on Atlantis were born.

So I'm going to assume he's talking about Star Trek, since its the best known and most iconic space science fiction show, and its history somewhat parallels that of the space program.

Just so's you know I'm not taking him entirely out of context, here's what he's quoted as saying:

"I blame the fantastic and unbelievable shows about space flight and rocket ships that are on today. All the shows where they beam people around and things like that have made young people think that that is what the space program should be doing. It's not realistic."

and later in the article:

"But, if you start dealing with fantasy and beaming people up and down and traveling seven times the speed of light, you are doing damage. You're not helping. You have young people who have got expectations that are far unrealistic, and you can't possibly live up to the expectations you have created in young people. Why do they get bored with the space program? That's why."


Can't have those young people stretching their imaginations and developing unrealistic expectations, can we? Good grief. Next thing you know, he'll be going on about the sins of dancing and the dangers of "the rock and roll."


Seems to me, Buzz, that if some young people, scientists and engineers, had not developed unrealistic expectations based on the unrealistic works of Jules Verne and H.G. Wells, there might never have been rockets into space.

Though Verne is credited with being highly predictive of the Apollo program in many respects, he shot his adventurers to the moon with a giant cannon, something even an engineer of the time could have shown was impossible. Verne, in turn, scoffed at Wells, who sent his travelers to the Moon using an "unrealistic" anti-gravity metal. (This debate is not a new one.)

Many later space program participants also cite the Mars books of Edgar Rice Burroughs as inspiration, which were even more fantastic and romantic. His hero, John Carter, travels to Mars through some kind of ill-defined astral projection, and his Mars is populated with all manner of fantastic creatures and races, including one that happens to have hot (yet egg-laying) females with whom Carter can conveniently interbreed. (Thus, I suppose, clearing the way for Captain Kirk to later bed-hop across the galaxy.)

And of course from there we can go the the Lensmen books of E.E. Doc Smith, or the juvenile novels of Robert Heinlein, for example. Smith's books are as fantastic, in their way, as Burroughs. Heinlein tried to be more realistic, but his books are still full of aliens and rockets flitting from star-to-star.

Yet this sort of stuff has managed to somehow inspire generation after generation of scientists, engineers, pilots, space advocates, and yes, even astronauts. In fact, many of the current crop site Star Trek, and the even-more-fantastic Star Wars, as inspirations.

The fact is, Buzz has it all wrong. Realism isn't the issue. Scientific accuracy isn't the issue. Science fiction is inspiring to those who make real space travel possible, and it's inspiring for entirely different reasons.

Star Trek offered hope that humans could go to the stars, that there might be other life in the universe, and that we would find it, and it would ultimately be good. It also offered the hope that humans could solve enough of our internal struggles to survive and work together to make it possible.

The how of getting there isn't important, it's the hope, the wonder, that we could. Once you've embraced that, you don't look around and say, "well, I can't beam to space, so I'm not going." No, you go and find the next nearest thing you can, the Shuttle, Spaceship One, the new Orion vehicle, and you try and get on it if you can.

And if that isn't good enough, you roll up your sleeves and try to make something better. Not the Enterprise probably. Not a transporter. But better.

Or at least, you hope somebody else does, and you're much more likely to support them if they say they're trying.

No, I'm afraid Buzz has it all wrong.

Not that I can blame him for his frustration, maybe even anger at our lack of progress in space, and the public's seeming apathy towards it. It's just that he's lashing out in the wrong direction.

The reasons for the public's lack of interest are complex, and I don't think there's one single thing to blame. But if fingers are to be pointed, I think you can start with NASA's stunning ability to counter-promote itself. We're not just talking inability to promote here. We're talking an exhaustive 40+ year campaign to dehumanize its astronauts into bland, interchangable drones in the public eye, and to make some of the most exciting voyages of adventure in human history, seem boring.

Buzz has always been one to buck that trend. Unlike some of the Apollo astronauts, he's not been reclusive, or allowed himself to be one of NASAs obedient PR pawns. He's been out there, in the public eye, pushing himself as an individual, and yeah, even licensing his image for toys, models and other trinkets.

Even signing on to host TV shows. Yeah.

And I've always backed him on that, because the astronauts should be rewarded for their courage, celebrated for their place in history, and appreciated as the deep and complex human beings that they are. If that means Buzz Aldrin Action figures, well, that's fine, because I want a Buzz Aldrin action figure, and I want one for my grandkid too. I want to know their stories, the good and bad of them. If they have something to say, I want to listen. And if they make a little cash along the way, more power to them. Who do I make the check out to?

But this time, Buzz is just wrong. He just doesn't know what he's talking about.

We should be thankful for Star Trek and Stargate and Star Wars and all the rest, that kept people thinking about the future, thinking about the stars, thinking about the planets, and not thinking about "if," but only "how, and when?" Because it's only through that spark of hope that we'll get there, however we do it.

And I'll take that spark any way I can get it, thank-you...

(While most responses to this post have been supportive and positive, not everyone was convinced. So I put some of my cast-off arguments into a follow-up post that I hope will put the matter to rest. Check it out.)

Thursday, June 19, 2008

A Thumbnail Cover Gallery


Click on the picture for a larger version.

A while back I started collecting recent covers from books in which Chris and I were published and combined them into a single graphic to use as a backdrop for our oft-neglected web-page. I realized today that I hadn't updated it in a long time, so I wasted several hours this afternoon tracking down covers (new ones, and old ones that I hadn't included before), resizing, and editing them in.

This is what I came up with. It still isn't complete. For example, I can think of at least four anthologies that aren't included (with several more coming before the year is out), plus a computer game (yeah, there are already two computer games in the grid that I wrote for), and a non-fiction book. I'll add another row later this year if I think of it.

It's been my experience that if you write and publish enough, you quickly start to forget things that you did, even if they were only a few years ago. Having an "at a glance" cover gallery like this is a bit of an ego booster, and a reminder on the hard days that you have accomplished something.

Wednesday, May 14, 2008

Borrowing Against the Future

One of the most powerful tools the right has used to pull the wool over America's eyes these last many years has been their ability to define the terms used to discuss key issues like the economy. One of my favorite examples is "tax and spend."

It's been a rallying-cry of conservatives for years, and a knee-jerk tag to attach to anyone of liberal stripe.

But what does it mean?

Almost nothing, actually.

First of all, while liberals do tax and spend, so do conservatives, especially the spend part.

But what's missing from the phrase is the wonderful loop-hole that conservatives so often skate through. If we keep repeating "tax and spend" over and over (and it appears so often in the media, political advertising, and political speeches, that it feels like being stuck in a room-full of parrots all with the same trainer) it trends to frame all our thinking on government spending and taxation. "Tax and Spend" implies that those are the only two options, and that isn't at all the case.

Okay, the spend part of the equation is pretty accurate. Show me a politician who doesn't spend. Left, right, I don't care. Show me one. I'll go wait.

Pretty hard to find, aren't they? Actually, we pretty much hire politicians to spend, much as we hate the idea. They're there to administer our collective will and resources to solve problems too big to solve ourselves, and too important to ignore. conservatives and liberals (and even fiscal conservatives and some other kinds of conservatives) differ greatly on how these things are defined, and that's a legitimate area of debate, which is probably why the political machine has chosen to avoid it.

Taxing, on the other hand, is far from the only option on how to fund that spending. But it's significant in that it's the most direct and honest way of funding the government, and we can't have that, can we?

Governments, on the other hand, can borrow money, or issue bonds, which is just another form of borrowing. Sure, these just defer the eventual payment, and make it more expensive in the long run, but like running up your personal credit-card, it somehow feels like free money, something that a straight-forward tax is never going to be.

Now sure, there are legitimate reasons for governments to borrow and issue bonds, but it's the "candy-coating" factor that I'm talking about. "No money down! No payments for 90 days! What will you do with all the money you save?" Republicans spend (in different amounts, and on different things, but spending is spending) just like Democrats do. What's different is in how they choose to pay (or often not pay) for what they spend, and how carefully they obscure the facts of that payback.

Okay, I'm getting a bit side-tracked here, as I'd actually like to talk about a specific kind of "obscured borrowing," one I consider the sneakiest, most insidious, and most destructive of all. Call it borrowing against infrastructure. Call it borrowing against the future.

How this works is simple. Governments have assets, usually lots of assets. Buildings, land, vehicles, bridges, subways, equipment, computers, weapons, pipes, wires, office supplies, all kinds of things. But few of these assets are of fixed value. Many things depreciate just sitting there. Others wear out or are depleted as they're used. And most require maintenance, otherwise they depreciate faster and wear out faster. Also, in most governments these assets need regular updating, both to keep things current, and to adjust capacity of government services to follow rising (or changing) populations.

There are other kinds of assets as well that are even less obvious. Employees for example. It's hard to think of the stereotypical, under-motivated government worker as an asset, but each one represents a bank of experience, knowledge and training that would have to be replaced right along with the body. Yes, some employees are much more valuable than others, and some are much more expensive to replace. We'll get back to that.

When you run up financial debts, it's pretty obvious. When you issue bonds, its there for everyone to see. And when you raise taxes or fees, everyone screams. But all this other stuff I've mentioned is like an invisible bank account that politicians can dip into without creating much attention.

The easiest way is simply to defer maintenance. Stop fixing school roofs. Stop repairing bridges. Don't change the oil in government vehicles. Don't replace vehicles as they wear out. Don't paint. Don't repair. Don't fix.

Another way is to delay needed upgrades. Sewage plant over-burdened? Why worry? So what if you have to dump raw sewage into the river every time it rains? And if the EPA wants to fine you, well, blame it on the liberals... Fact is, most any such crisis of capacity is usually slow in coming. Almost universally it can be pushed past the next election cycle, and with luck, until term-limits kick in. Then it becomes someone else's problem (hopefully, the other party's).

The massive application of this strategy dates back to the Reagan administration, which just stopped spending money on infrastructure. We're, in many cases, only now seeing the fall-out (no pun intended) from that policy today, with collapsing bridges, crumbling roads, and failing levies. You've got to give some grudging respect. All than invisible borrowing deferred to not only decades after Reagan left office, but until he is several years safe in his grave.

And since our national government tends to change hands periodically, if you can simply stall long enough, any debts you run up will simply get handed off to the other party, who can take the blame if they actually to raise funds to pay off your debts. Yet another implication of "tax and spend" is that the person or party doing the taxing is also the person or party who did the spending, but very often that is not the case.

Reagan ran up the debt, Bush I ran it up more, Clinton paid it down (more than canceling out the Bush I years) and now Bush II has run it up to unprecedented levels.

Speaking of, a more contemporary (and far more contemptible) example of borrowing against the future is to be found in current US war in the middle-east. Of course, the obvious up-front costs of the war are already eye-bleedingly staggering (if there were some sort of Oscar for Government Spending, George W. Bush would certainly deserve the statue), but there are equally staggering hidden cost here.

The war has been grinding our military down to a nub. Equipment is wearing out at a phenomenal rate. Stockpiles of ammunition, equipment, and supplies (a lot of this stuff in turn left-over from the Cold-war era) have been drawn down and not replaced. Sooner or later, all this junk will have to be repaired or replaced, and somebody will have to pay for it.

But to my mind, the really tragic cost, the one that makes me want to spit, is the human one. This war has been run on the backs of National Guard and reserve units who have been deployed again and again and again in a way that nobody, a few decades ago, would have ever imagined happening short of an alien invasion or World War Three. These people, even the most loyal and determined of them, are exhausted. Most of them have to be thinking that, by now, they've more than done their service to their country, and I don't see how you can argue with them.

For many of them, they're going to take the earliest opportunity to get out of the service, and that means losing their experience and training.

Remember when I said a while back that some government employees are more valuable than others? Well, there are few more valuable than the modern military man or woman. The day of the ignorant grunt is over. The typical modern soldier is a highly trained technical expert not easily, quickly, or cheaply replaced. I'm finding good numbers hard to come by, but it seems safe to say that even the most basic infantryman has several hundred thousand dollars invested in them, and on the other extreme, a fighter pilot's costs are likely well north of two million dollars.

There's also the simple fact that combat veterans have an experience and perspective that can't be obtained through training at any cost, and to which a monetary value can't be assigned. The men and women who fight future conflicts and defend our shores need these experienced fighters, and we're pissing them away.

When you drive people out of the service, and we're doing so on an epic scale, you're most certainly borrowing against the future.

Of course, this only considers the people who are able to walk out of service whole and hearty (and bless them, I wish it was every one), but there are many more who come home with shattered bodies and injured minds, or who simply come home in a flag-draped box. To those people (or their survivors) we owe compensation for their sacrifices. To my mind, when you've borrowed against a soldier's life and future, this is (or should be) an immediate pay-back time.

Sadly, we still hear again and again of nightmarishly run-down medical facilities, of injured veterans denied benefits and proper medical treatment, even of the bodies of returning soldiers being treated with disrespect because somebody found a way to cut corners on the processing.

This makes my eyes red. If you're going to do this thing, run out the national debt, raise taxes, do what it takes, but don't try to hide your spending by putting it on the backs of the very people who have fought the war.

I know that "honesty" and "politician" are two words that rarely interact, but I think the Republicans have pushed fiscal deception to an unprecedented level. It's time for a hard, hard correction. I suggest when election time comes in November, that if you want any possibility of fiscal responsibility and accountability, you look for someone with the "tax and spend" label attached to them.

Sure, you may not agree with them on every detail, but it's right there on the table: what to tax, what to spend, and what to spend it on. From there you can negotiate.

The option is be left eternally wondering what the Republicans are borrowing, how they're borrowing it, who they're borrowing it from, and when you are going to have to pay it back.

Tuesday, February 12, 2008

What is Science Fiction Anyway, and Does it Matter?


Just stumbled on this (to me) very annoying essay that attempts to ever more narrowly define what is "real" science-fiction.

I'm annoyed on multiple levels, starting with the idea that this distinction is somehow important, moving on through how the author seems to think "real" sf is somehow superior, just on principle, to that Tolkien and Harry Potter crap, and continuing on from there.

I do, however, think there's some interesting validity to the author's idea of an scientific “event horizon” that defines whither a science fiction story is technically plausible or not. His idea is that the line between science fiction and fantasy (his term, though I think “science fantasy” is more correct, if a distinction must be made) isn’t a static thing, that a story can be written as science fiction based on the best scientific knowledge of the day, and be turned into science fantasy after the fact as science marches on.

Yet his central premise is that most sf produced today, especially media sf, actually starts out inside his speculative "event horizon," that most of it is scientifically implausible by today’s science (and probably yesterday’s as well) not tomorrow’s.

Okay, actually, I agree with this too. Where I differ is that this is somehow a bad thing. I think it's time to embrace it, fess up to the fact that it’s absurd to think that (as an example) Star Trek is, an any way more than metaphorical, any kind of prediction of the future, and that as long as we enjoy the stories, that's FINE.

First of all, I'm of the opinion that a good story rarely starts out, "An idea walked into a room." That notion has damaged sf as a literary form more than any single thing. Stories are about people, and if an idea enters into it, it is how the people react to that idea which is involving to the reader. The idea may be interesting as well, but a story is not simply a science-fact essay with dialog and a villain. This is important, because if the story is good, the failure of the science (by time or intentional design, at least, not withstanding the author's ignorance) will not significantly diminish it.

Frankly, I think that science fiction's function as a literary crystal ball predicting the future has always been highly over-rated. For starters, "science fiction" is a misnomer. Science fiction CAN'T predict science, except through guess-work, and where sf has attempted to anticipate hard science, it has almost always been wrong. Making up undiscovered subatomic particles is just fantasy with sf trappings. Even speculating about predicted-but-undiscovered particles (such as the Higgs Boson) is questionable, because, even if they exist, most likely anything you say about it will be wrong (and is likely to be proven so within a few years).

Most of what we think of as "science" in science fiction stories is applied engineering and technology, and it IS possible to extrapolate these things, to some limited extent. Jules Vern, for instance, didn't predict the submarine, or even its use in war. But he did extrapolate the submarine into a capable and useful vehicle and consider how it could be used for good (exploration, access to aquatic resources) and evil (terror attacks on shipping). He predicted lunar travel, but even by the science and engineering of his time, his technology was fatally flawed. The story's predictive value is not in that his science or technology were correct, but rather in its (quite correct) assurance that the technology COULD solve the problems involved with enough time and effort.

It’s ironic that Vern then scoffed at H.G. Wells book on lunar travel because he relied on anti-gravity metals and other such implausible devices. Yet neither book holds up to modern science, and the flaws in Vern's work are much more obvious and easier to prove. Yet Vern’s work is also satisfying in part in the his method for reaching the moon, though scientifically flawed, is at least plausible and understandable. Never mind that it would never reach the moon, and even if it did, it’s passengers would be nothing more than jelly due to the incredible acceleration. The method allows even the modern reader to willingly suspend their disbelief.

Classic Star Trek is sometimes given credit for "inventing" the cell phone. Yet all it really predicted was the shape and size of a cell phone, not the technology that makes one work, or the science behind it, or even the functional way in which a cell phone works. Functionally, near as we can tell, a Star Trek communicator was just a WWII walkie-talkie decreased in size, and increased in power. Actually, what it did, how it worked, and what those little dials and buttons did is all rather vague. From a story standpoint, that's actually good, as in being vague, it has dated less than a more scientifically-grounded device would. It served a story purpose, and served it well.

Really, that’s all most early Star Trek technology was, story devices dressed up with flashing lights, buttons, and sound-effects. Look at the elegant, self-descriptive names of those devices: transporter, communicator, shuttlecraft, warp drive, impulse engines, photon-torpedoes, phaser, tricorder. A transporter is less a teleportation device than a method of moving characters rapidly through the story (and without the expensive special-effects necessary to show a spaceship landing). A shuttlecraft isn’t a form of transportation at all, it’s a bottle to stuff a couple-or-three characters into and then crash into a planet for story purposes. A communicator is a delivery device for exposition (and so is a tricorder, for that matter). And so on…

Science Fiction was born in an age when science was expanding into a vast unknown, and when technology was advancing in absolute terms. But while technology moved slowly (by modern standards) in those days, it pushed regularlly into new realms, and seemed able to advance without limits. These days, things are much different. Technology is moving so fast these days than any such speculation is almost certain to be rendered either wrong or obsolete in very short order. And fast as it moves, it does not heave blindly into the darkness.

We live in a world where science bounds us at every turn by provable or demonstrated limits. The speed of light seems much more absolute than it once did, and time-travel far more likely to be an absolute fantasy. The list of unknown scientific things to speculate about grows ever shorter. Even the day in which you could imagine planets at random around known stars is growing to a close. We're mapping distant star systems, with new planets discovered almost every week. There are still gaps in our understanding of physics, but they're relatively small, and their practical implications far less profound than the heady days of the atomic era.

Computers continue to advance, but in such regular and predictable ways that the progress has gone on for decades, regular as a clock, far more predictable as the weather. Yes, we can speculate about artificial intelligence, or robots, but we've been speculating about those things for a very long time without a clear grasp of the technology that might make it possible. Are Asimov's robots no longer valid because of that? Hal 9000? Frankenstein's creature? The Golem?

Really, some of the best and most enduring sf isn't even about technology, it's about society and culture. A good example is, unfortunately, a story I can't name. I think it's a Bradbury story (though it might be Asimov, or someone totally different, I haven't read it in a long time). This is from memory, so forgive me if I get the details wrong, but here's my recollection about the story. It's about a future world where everyone gets from place to place using teleportation doorways, and as a result, culture has evolved to a point where nobody goes outside any more. One day a household's door breaks, and a boy walks to school. He discovers that he LIKES going outside, and even when the teleportation door is fixed, he continues to go outside. His concerned parents, of course, try to break him of this aberration. My memory of the ending is vague, except that the pleasures of going outside won't go away, and the idea spreads...

Looking at this from a scientific standpoint, it's kind of absurd. Science is showing us that certain kinds of "teleportation" may be possible, but the idea that we'll be routinely teleporting people from door-to-door is highly unlikely. The energies involved are incredible, for starters. Quantum uncertainty is another huge issue. But the story is no less valid because of this. In fact, it may have become MORE valid with time. We might turn into these people, even if the technologies responsible aren't teleportation, but some combination telecommuting, the internet, console gaming, robotic cars and general paranoia. In fact, to some extent, we're well along the way to turning into these people. The story still works as a metaphor for that. It doesn't matter if teleportation doors are possible by the most current version of physics or not. It doesn't matter if the story had used magic mirrors instead of teleportation doors.

Or look at Jack Williamson's "With Folded Hands." If you haven't read this story, you should. It's about a man who discoverers a new store in town, one selling household robots. The robots are black, sleek, beautiful, and perfect. They clean house. They run errands. They do chores. They wait on their owners hand and foot. And they are completely incapable of harming humans. They EXIST to protect us from harm. It is their primary function. Never mind where they come from. Never mind how they work. Not really important.

Of course, there's a catch. The robots are TOO perfect. They move in and take away all human want, all human suffering, and in the process, all human freedom. Humans become prisoners of safety, not even allowed a knife to cut their food, least they injure themselves or others. The hero realizes this, tries to thwart them, but it's too late.

As I said, not so important how the robots work or where they come from (space, presumably from some non-existent planet via non-existent FTL). It isn't important how likely real robots are to be human-shaped or not. It isn't important if robots could really take over this way. The story is more valid than ever because it's about the slippery slope of trading freedom from comfort and an illusion of safety. It doesn't matter if the "safety" takes the form of a sleek-black-robot or a border-line fascist government, or helpful fairies that help too much. It's the sort of thing every school kid in American should have been reading post 9-11, every voter should read before choosing their next president. It's a story WITH robots, not a story ABOUT robots. That's an important distinction, and one that's lost on a lot of sf purists.

Sometimes a science-fiction can even be accurately predictive in ways that have nothing to do with the scientific device in the story. In 1971 hard-sf writer Larry Niven published a novella titled “Flash Crowd.” The story is set in a world where teleportation booths make instantaneous travel anywhere in the world possible. The basic premise is that with live television reporting of breaking events, people would naturally jump into a teleportation booth to see things for themselves. The result: instant crowd, instant mob, and potential instant riot.

In fact, “flash crowds” did happen, and they didn’t require teleportation. Live coverage of TV did play a role in some real “flash crowds” but the cell phone turned out to be a far more effective device for creating them. Ask the teen in the news a while back who threw an adult-free party at his house and invited a few friends. Apparently they invited a few friends as well, and they told other friends, and so on, until the police had to be called to break up a near riot of hundreds of teens converging on the home, drawn there by an invisible web of phone calls and text messages.

The point here is that, who cares if teleportation is possible or not, or if real teleportation would ever look or work like Niven’s teleportation booths? That isn’t where the predictive value of the story is at all. It was a “what-if” thought problem that translated to the real world in a completely different form.

If we define science fiction and fantasy as stories built on the premise or "what if?" and If science fiction (valid science fiction) is defined purely as a "what if" story that "could happen" then we're left with a pretty narrow field indeed, an even the stories that pass this litmus test are inevitably headed rapidly into the dust-bin of history, to join the huge pool of "real" science-fiction that's gone before. Whole subgenres, such as alternate history, are excluded from the canon as well. (Yes, you can scientifically justify alternate history through some application of the "many worlds" theory, but few books in the genre even bother. And of those, I rarely see it as more than tissue-thin rationalization; science as window-dressing.)

Really, for science fiction and fantasy I think the important distinction is not "could this happen," but how willing and able the reader is to BELIEVE that it could (or did) happen for the purpose of, and duration of the story: the suspension of disbelief. Fantasy has its roots in myth and legend, in a time when monsters, gods, and magic were, if not believed, then no less incredible than FTL drives or time machines are to most modern readers. Science fiction was born out of time when science and technology had largely replaced those things and in the realm of "fantastic but credible" in the public consciousness. (There was still religion, of course, but speculating about religion has always been and remains to this day, a dangerous pursuit, more likely to enrage than enlighten.)

Mind you, it isn't important to REALLY make the reader believe in the fantastic elements of the story. They can enjoy and be moved by Lord of the Rings without thinking that Middle Earth is historical truth, or that orcs and elves are real. They need only be willing to embrace them in the context of the work. The same is true of science fiction. It really doesn't matter if teleportation doors or warp drives work or not, only that the reader is willing to believe them in the context of the story. If scientific or technological trappings make that easier, then so be it.

In fact, a distinction one could make of fantasy is that the average reader has the comfort of putting down the book and knowing that the fantastic things they're just read are NOT possible. The story mentioned could make the same point with magic mirrors as with teleportation doors, but would it have the same impact if the reader could so casually dismiss it in the end? Perhaps not. But that distance also has its advantages. "The Golden Compass" can write about religion (like I said, dangerous) in a way that might not be possible in a science-fiction book, or even in non-genre fiction. The subject is dangerous, but there's the emotional and societal safety-valve that it "isn't real," making such an examination much more palatable than it would otherwise. This is true of any hot-button topic. A little distance, the different perspective provided by a science fiction or fantasy context, makes it a bit easier to approach objectively. It's a bit of trickery that Jonathan Swift understood well almost 300 years ago, and it's still valid today.

Likewise, there's great value in allowing the reader to believe that a thing could be possible. "From the Earth to the Moon" is important, not because it accurately shows how a trip to the Moon might be made, but because it makes it credible that through industry and determination, such a thing IS possible, even if the details differ. Compare that to Star Trek. We know that space travel, even to distant stars, IS possible. And while I can say with some certainty that our methods of accomplishing this will not resemble the Starship Enterprise, that the explorers aren't likely to have much in common with Kirk and McCoy, and that the aliens will almost certainly not resemble Mr. Spock, that DOESN'T MATTER. We can understand and identify with Star Trek far more easily than we can, for instance, post-human intelligences spending centuries traveling between stars in "spaceships" that resemble silicon cobwebs thousands of miles across.

If Star Trek makes us believe that such voyages, through industry and determination are possible and desirable, then the rest is just window dressing. Details. And though science fiction can't predict how, we will get there someday.

Wednesday, December 05, 2007

The Darwinism of the Wind

Update to this post: 12/07/07 - See added note at the end of the post for additional information.)
Well, the worst storm in at least 20 years here on the Oregon coast is gone. The power came back on last night, and we have phones again (though with limited service) and internet. It's really nice to be back in the 21st century. Really nice.

Here we got some rain, but the brunt of the damage came from wind. Gusts, depending on who you listen to, were either as high as 125 or 129MPH. I think 125 is the official number. We're the lucky ones. Just north of us they got the rain, often 10-12 inches in just a few hours. You can resist the wind, but when water is determined, there's no stopping it. Those people have been devastated.



I drove around town this morning with camera at hand. I was surprised to see how quickly repairs and clean-up were progressing. A destroyed billboard had already been cleaned up. As you can see in the pictures, the gaping hole in the side of the local Casino was already being patched. Chain-saws, bucket lifts, and service trucks were everywhere.



Another thing that surprised me, given the extreme winds, wash how little real damage I could find. There were plenty of trees down, many ripped up by the roots or snapped off at the base. But very few structures were significantly damaged. There were a few broken windows from flying debris, lots of damaged roofs, and a few freakish things like the damaged wall at the Casino (and in that case I have to wonder if it was already weakened somehow, possibly by water leaking inside the wall).



There was lots of damage to signs, of course. It seemed like half the business signs in town were down or seriously damaged. But for the most part, unless they happened to be in the path of a falling tree (none of the ones I saw were, but I did hear of this happening) there was very little visible structural damage.



In most any other town, winds like these would have flattened the place, but it didn't happen here. The reason, is the Darwinism of the wind. We have storms here every winter. Locals really don't even pay any notice to the wind if it's under 60MPH. Below that, it's more an annoyance (blown-away trash cans, flattened winter flowers in the garden, and a few power outages) than a real threat.

For the most part, things that could be flattened by the wind were long ago flattened. Anything that could be blown away is long gone. The exceptions are, as mentioned, trees and signs, both of which tend to grown and age until the right gust of wind catches them and snaps them off.

Roof's age too, so damage there is inevitable, but usually not serious. By necessity, things are built strong here. My house has been standing up to these winds, three blocks off the beach and on top of a hill, for over fifty years. With luck, it will stand fifty more.



Thing is, when things fail here, they tend to fail catastrophically, especially in a storm as strong as this one. The Casino wall seen in previous pictures is a classic example of that. Somehow the wind got under the outer wall, and peeled that big building like a grape.

A less spectacular example is our big loss to the storm, a storage shed we bought last year. Yes there is (or used to be) a shed in this picture. Mostly what is left is the floor, some of the heavier contents, and a couple corner panels that remain attached. It was one of those pre-fab plastic jobs. It was surprisingly strong. I've never seen it move in our strongest winds before, and I watched it closely to be sure. But it just wasn't ready for triple-digit speeds. About midnight Sunday I saw that one of the side panels had popped out.

Chris and I ran out in a lull and moved the most vulnerable contents inside. But it was too late for the shed itself, as the most powerful part of the storm was still to hit, and with a hole in its side the wind could get under the roof, turning it into a sail. I knew the roof would go, it was only a matter of when. When the big gusts came, one of them lifted the roof off in one piece and deposited it in our front yard. The rest of the shed walls started to rapidly self-disassemble.



We ran out in heavy rain and wind (probably 70-80 gusts instead of 100) to grab the roof and drag it into a sheltered alley between two houses, so it didn't blow into someone's house or car and do more damage. We were lucky it didn't turn into a parasail and take both of us away, but we were successful.

Not happy for us, but looking around at people who lost homes or cars or even roofs, we were pretty lucky. We even managed to salvage all the pieces of the shed. I'll have to examine the parts carefully for damage, but it might even be possible to rebuild it. If we do, I'll be modifying it with all sorts of reinforcing straps and bolts to make it stronger. Worth a try anyway.

Because this is the coast, where only the strong survive.

(Update to this post: 12/07/07 When I took the picture of the Grocery Outlet store seen in the second picture, I thought the damage was only superficial loss of roofing on the facade. Turns out I should have looked through the windows. Water built up on the roof and caused a large part of the store's ceiling to collapse. As I said, when things happen, they tend to be catastrophic. The store has never suffered any noticeable storm damage in all the years I've lived here. Anyway, the store is now closed for major repairs with no word on when it will reopen.)

Tuesday, December 04, 2007

storm warning

We've just weathered the worst storm we've ever seen here on the Oregon coast. 129mph gusts reported here in our little town. Our house is okay, but our storage shed self-disassembled. Damaged and downed trees all over town. Roads blocked. No power, phones, or internet. I drove 30 miles to a coffee-shop where I could blog this quickly. Here are some pictures of local damage and some downed power lines around the corner from the house. No word when we'll get power or phones yet. The main lines into the city are down, and we don't know for sure even where the breaks are.

Locals Dean Wesley Smith, Kris Rusch, Dan Duval, Jerry Wolfe are all well and accounted for. More later.



Tuesday, November 13, 2007

Buy me the Moon



(Earthrise photos taken by the Kaguya probe, credit: Japan Space Exploration Agency)
As I've said before, people constantly over-estimate the cost of the Apollo lunar program. Not that it was cheap. It was a huge undertaking. But compared to many of the things big economies (like we have here in the United States) do, it just wasn't that big.

Today, a report by congressional Democrats pegged the cost of the wars in Iraq and Afghanistan so far at 1.6 Trillion dollars. The report is controversial, and Republicans are already calling for a retraction, but consider how it compares to the Apollo program.

By comparing various estimates as to the program's cost and running through cost-of-living calculators to adjust for inflation, I come up with a number of about 143.5 billion in 2007 dollars. Just for safety and simplicity, round it up to 160 billion dollars.

Now, keep in mind that a trillion has three more zeros in it than a billion. So if the report is right, our adventures in the middle-east have cost us as much as ten Apollo programs, and if its predictions are near correct, it will cost us over twenty Apollo programs by 2009.

But as I said, the report is controversial. Let's say it's wrong. Let's say it's a wild lie that inflates the actual cost of the war by a factor of ten. Then our war-of-the-moment has only cost us one Apollo program, and by the end of the decade, shouldn't cost us more than one or two more. That's much better.

Oh, one other factoid to consider. The Apollo program ran for 14 years, 1961 through 1975. We invaded Afghanistan in 2001 and the second Gulf war started in 2003. The report's projections only go through 2009. The Apollo program not only cost far less money, it was spread over a much longer time.

By the way, if you're curious, according to a recent Washington Post article, the inflation-adjusted cost for the Vietnam War was 549 billion dollars. And that was money well-spent, wasn't it?

A lot of people like to say we can't afford to go to Mars, or back to the Moon. Maybe they're right. But if so, it's important to consider why we can't afford it.

Hey, I've got an idea! Let's just cancel our next war and just build a Moon-base instead. Or to put it another way...

For decades, it's always stuck in my craw when I'd hear somebody say, "if we can put a man on the Moon, why can't we do 'X.'" Well, I think it's time to finally put that one to rest. I propose this replacement:

"If we can put an army in Iraq, why can't we put a man on the Moon?"

Wednesday, October 10, 2007

Geeks bearing gifts


Forgive me. I have done a Geek thing. I installed Linux on one of my computers here last night, and I'm here to share the tale.

This is a big thing. I'm a writer, and computers are (following in importance perhaps only the English language, a tool I frequently and shamelessly abuse) one of my primary tools. I rely on them not only for word processing, but for business communication (email), project delivery (email again), research (very, very important), record keeping, promotion, tax preparation, almost everything to do with my web comic Minions at Work (except the Minions themselves) and that's just for starters.

There was a time that was pretty simple. Chris and I shared one computer back in the day (though that was before she started writing seriously), first CP/M (remember CP/M? No? I guess I am getting old...) then later MS-DOS, and then Windows. Everything, including the early Windows computers didn't require much upkeep. You installed software once (if it wasn't already installed on the machine when you got it) and forgot about it.

But upkeep has become and increasing burden. Software updates come weekly now, often whether you want them or not. Windows updates itself. So does the Norton security software. But there there's the browser, the media players, the browser plug-ins, all the Microsoft Office programs, all downloading, installing, hogging the computer's resources in the process, usually wanting to reboot when it's least convenient, and often causing other problems in the process. Each of these updates, we are assured is important, even vital. Most cover security issues, and we all know the threats are real. Despite all of this, my computer, probably the best-maintained machine in the place, still managed to get infected with adware a few weeks ago.

And it isn't just one machine. Oh, no. There are just two of us here in the house, Chris and I, but we have a bunch of computers. Four working desktops at the moment, and I think three laptops. There are computers in each office, a computer in the guest-room (which is also a backup), another desktop that may serve as a backup or a file server in the near future, a main laptop, and a couple of older machines as backup for that.

All of these are Win-boxes, all in need of constant care and feeding that some of them just don't get. I'm mostly the IT guy here, and I don't do nearly enough. Plus, all of them need security software, and that needs to be replaced, at considerable expense, annually. Worse, some of the older machines are still running Windows 98, which is no longer supported by Microsoft, and worse, by Norton, so there are suddenly these unsecured computers on my network, infrequently used, but still inviting trouble.

Something has to give. I'm tired of the update treadmill, and while lots of the old hardware we have here just keeps chugging along, its the software that wears out, and it matters not how little we use it. Turn on a computer you haven't used in six months, you still need six months worth of updates, if you can even get them.

"So," I can hear many of you saying, "you really need to get a Macintosh." Some of my best friends are Mac people, and I hear plenty of this in lunch and diner conversation.

Nope. I can tell you right now, I'm not going there. It isn't that I don't think Apple products are good. Most of them are. And they do solve a lot of problems in the short-term. Mainly it's that I'm of the unshakable opinion that Apple is an evil company. Now, sure, Microsoft is evil too. But everybody knows it, including all their customers and even their most loyal supporters. Microsoft doesn't even flat-out deny it, though they dance around the subject.

But my Apple friends are in blissful denial about the evil that is Apple. Apple is arrogant, monopolistic, anti-competitive, and most disturbing for me as a writer, seeking to establish a stranglehold over the distribution of intellectual property and then lock it into their hardware.

Making them, I guess, not much worse than any other large corporation. But what really disturbs me is the response of their average customer, which seems to be, "please, sir, may we have some more?" I'll consider putting a Mac on my desk the day I can buy a song from iTunes and put it on my Creative media player.

Which is not a blanket condemnation of Apple products or customers. Some of you know the devil you're dancing with, and that's fine. And there are plenty of people who, at this point, probably should never buy any computer other than a Macintosh. They're great for people with minimal technical aptitude and little time to fiddle, and who just need a smooth, easy, reliable computer experience at any price.

In fact, listening to my mom struggling (she lives diagonally across the country from me, with one phone line and a slow dial-up connection, so there isn't much I can do directly to help) to update to a new version of Norton, I found myself really wishing I'd told her to buy a Mac when she replaced her last PC. It would have required her to relearn a lot of things, but I think she could have managed it, and staying secure and stable using a dial-up connection would have been much less of an issue.

But there are unlikely to be any Macs in this house any time soon. We shall not speak of it again.

Up until recently I told myself that as long as I kept our primary hardware and software reasonably current, the problem would stay under control. The problems came only when we let things (like Windows 98) fall too far behind the technology curve. But due to a hardware failure, we recently replaced Chris' computer with a new Dell and Windows Vista.

You know Vista, the operating system that's supposed to be all stable and secure? Well, bloated and annoying seems to be more the case. I haven't been exposed to it much, and Chris' seems satisfied enough with her machine at the moment, but I've seen enough to suspect that it's just a continuation of the problem (and buying deeper into the Microsoft evil) rather than a solution, and it's no solution at all for our older machines. Even if they'd run Vista, it's just too damned expensive, difficult, and risky to update.

And one thing that has increasingly bothered me about both Apple and Microsoft is how much you no longer own the technology, it owns you. Look at the Apple customers who unlocked their iPhones (that probably never should have been locked in the first place) only to have them turned into "iBricks" at Apple's earliest convenience. Look at Microsoft's "Genuine Advantage," a bit of spyware that assumes your copy of Windows is pirated until proven otherwise, and then subjects your computer to a cavity search every time you want even the most minimal support, and which has already locked down the computers of countless owners of legal and legitimate Windows installations.

Ever notice how every new piece of software, and many of those countless updates, comes with a new terms-of-service agreement? Do you read them before clicking the accept button? Of course not. Nobody does. Would you understand them if you did? Unless you're a lawyer, no, and possibly not even then. These guys have their hooks into us, and they keep reeling in the line. It's not only infuriating and insulting, it's frightening, considering how much of our modern world depends on one of those two technology companies.



Which, along with other things, has had me thinking about Linux for a while. Based on internet and media chatter, it sounded appealing. A free, secure, stable operating system that operates on an open-source license that won't make you an indentured servant to Bill Gates or Steve Jobs. Plus, plenty of free software to choose from. In fact, it sounds almost too good to be true, which always makes me suspicious.

So, I keep hearing good buzz, but my last exposure to Unix-like operating systems was back in the command-line-driven days. I used command-line operating systems (MS-DOS, the afore-mentioned CP/M, and a variety of other early personal computer DOSes) for years, but I had no desire to learn another one.

Oh, sure, I knew there were graphical, windowing shells, but I was put off by the idea that there would be a technically complicated installation process. But more recently, the buzz has been that Linux is nearly ready for the mainstream, that there were versions that featured clean, automated installations and refined interfaces that hid most of the geeky stuff from the user. But (this is another thing I dislike about the Mac) all the geek stuff is still there. If you need to, or if you want to, you can "pop the hood" and poke around in the guts of the system at any time. I like that, even if I never have to use it.

Finally, the Linux guys had me intrigued enough to do something. The old Compaq in the guest-room hadn't been turned on in months, and its outdated Norton and Windows 98 operating system had turned it into a critical security issue if I ever did need to use it. It really didn't have any data on it that I was worried about losing, and if the installation failed, it really wasn't going to become much less useful than it already way. It was too old to bother with any significant hardware upgrades, and Chris' old Dell (running still-maintainable Windows XP) was probably going to replace it as soon as I got around to replacing a fried hard-drive.

Given that there wasn't a lot to lose, I really didn't sweat a lot over which of the zillion versions of Linux to download. My research mostly consisted of looking up Linux on the-often-unreliable-Wikipedia and looking for buzz-phrases like "stable" and "user-friendly installation." I finally decided to try Ubuntu, since it was based on Debian (which I'd heard of) only supposedly with more emphasis on usability. Also, you could supposedly try it without actually installing it by creating a bootable Ubuntu CD-ROM.

This wasn't very successful for me. First, I found the slowest server in the world (despite the fact that it's located only a few hundred miles from me) to download the 600+ megabyte disk image from. Then, when I tried to run it on the Compaq, it would grind on for a long time, display some pretty logos, then crash down to a command line where I was utterly lost.


To be fair, this is probably the fault of my old and eccentric hardware, and I never actually tried to install Ubuntu, just run it from the CD-ROM. Your experience may be much different. However, rather than dink with it, I decided to try another implementation. I decided to try Debian itself, as it had been praised by at least one Linux-user I'd talked directly to.

Debian didn't offer the "run from CD-ROM" option, but they did offer a "net installation" CD-ROM image that was much smaller (about 140 megs, I think). It required the target machine to have a high-speed Internet connection during the installation, but I had that covered. I downloaded the disk image file onto our primary laptop, along with a free disk-burning program the Debian folks recommended. This latter program allowed me to turn the disk image into a bootable installation CD-ROM, and it ran without a hitch.

I put the disk in the Compaq, turned it on, and watched it go. I was expecting problems, as I hadn't bothered to even investigate Linux drivers for the machine or any of its components (network card, graphics card, printer, sound-card, etc.).

The installer is text-based and pretty simple. If you're installing it as the only OS on a machine with no existing data on the hard disk you need to save, you shouldn't have to tell it much more than "go." I, however, wanted to try and preserve a Windows partition so I could keep that as a backup in the installation failed.

The installer included some pretty slick partitioning software, so I repartitioned the old 10 gig drive to allow a minimal 2 gigs for the Linux installation. I knew that Linux was supposed to be much more efficient than Windows, but this was only a blind guess. The installer automatically divided this up into two partitions, one for the installation, and a smaller one for swap files.

Let me stress that this is technical crap that you can avoid by just allowing Linux to completely take over the system, or at least a particular drive. I made things harder for myself than they needed to be.

The installation took quite a while, though it was no more long or troublesome than any of the many Windows installations I've been through. In fact, it was easier in that I never had to swap disks. Debian pulled everything it needed off the Internet.

Problem was, my first attempt at installation failed. It told me where it failed, in the process of installing application software, but it told me nothing at all about why. Now, it appears that at the point of failure, Linux itself had already installed just fine. I soft landed in a text menu of the install program, and it encouraged me to repeat the process manually, hopeful that it would somehow work the second time. But, it didn't, and neither did the following process, which was to set up the operating system to boot. Again, no information on why, not even a cryptic error code or number.

But I had a guess, which I suspect was probably right. I think it ran out of disk space. I restarted the process, partitioned the disk to give 3-gigs total to Linux, and tried again. It went through the process this time without a hitch. There were a couple of questions and prompts along the way that gave me pause, and might have sent a less technically savvy user into a panic. I had to come up with passwords (both an individual password, and an administrator password), an individual user name. I had to give the computer a name, and a domain name (not much of an issue unless, like me, you're trying to make it talk to an existing network of computers at your location).

But for the most part, it worked in an almost magical way. In any given Windows installation I've done, I've needed at some point to track down one (or more often many) hardware driver disks or track them down on web-sites. Here, it never happened. The installer seems to have recognized all my hardware and found the appropriate drivers on its own.

The moment of truth arrives. Following the prompts, I take out the CD-ROM and reboot the computer. It works! I have my first real look at Debian Linux!


In some ways, it's almost disappointingly familiar. It looks a lot like Windows, and most of the differences are pretty self-explanatory. I had no trouble finding and running applications, and navigating the files. It's slick, modern, and mouse driven. Oh, maybe the look isn't quite as sophisticated as a current version Windows or the Mac OS, but that's mostly window-dressing (no pun intended). If you've used either of those computers for a few years, you shouldn't have a bit of trouble here.

In terms of performance, it seemed fine, despite the old, slow, hardware and the minimal disk space I allowed it to have. (I'm sure that, like most operating systems, it would have run better with a faster processor, more memory, and more, faster, disk-space. On a even vaguely modern computer it seems to me that it would fairly scream, especially when compared to a resource-pig like Vista)

Did I say applications? Yes I did. One of the nifty things about these more user-friendly versions of Linux is that they give you the option of pre-installing software packages based on how you plan to use the computer. Debian gave me a lot of goodies to play with right out of the box. (Wait, there was no box! My bad!) First, there was an email program, several web-browers, and a BitTorrent-type file-sharing program. There was a whole list of mini-games of the sort that come with most Windows and Mac boxes (solitaire, blackjack, a mine game, a Tetris clone, and other time-wasters. There were video players, music players (for these latter two you'll probably need to download some decoders elsewhere, as these contain proprietary technology, and the Debian package includes only "open-source" software), picture viewers, and what is supposed to be a powerful PhotoShop clone.

Best of all, unlike most Windows computers you can buy, none of this is nag-ware, share-ware, spy-ware, ad-ware, cripple-ware, or any other flavor of no-ware. This is all full version, fully functional, no-strings-attached stuff.

And most importantly for the writer, it includes the open-source Microsoft Office clone, Open Office. I really haven't done much more than open this and poke around, but it looks fine for what most of us do. All the familiar formatting and editing tools seem to be there, and it reads and writes to all but maybe the very newest Microsoft Office formats (when submitting electronically, I always drop back to an older MS Office format anyway, as it avoids all sorts of potential compatibility problems). Moreover, it fully supports the "Open Office" formats which may better allow your documents to be used around the world.

It's really going to take a lot of use and transferring files back and forth with Microsoft systems to see if this is really ready for prime time as a professional writer's tool, but what I've seen so far is encouraging.

There's plenty of other Linux software out there too, much of it free and open-source. Are you going to be able to use your familiar applications on Linux? Quite likely not, but for the most common tasks, you'll probably find something similar, just about as good, and best of all, free.

This is an ongoing story. I doubt this is the last Linux installation I'll be doing here. One of the older laptops will probably be the next Guinea pig, and at some point, I might try to set up on one of the backup boxes as a file server for backups. For the foreseeable future, our two primary computers will probably still run some version of Windows. But I could at least imagine a day when the primary machines might at least be able to book Linux, and when maybe it might be just a backup computer running Windows, for those few instances when nothing else will do).

Is Linux ready for prime time? Should you consider it? My answer at this point is a definite "maybe." Installation still seems the greatest sticking point. Your installation could be great, and probably will be, but things will occasionally go wrong, and when they do, you could be on your own. Telephone or in-person access to an experienced Linux user is still probably a plus.

However, you can avoid this completely by buying a computer with Linux already installed. That's now an option, from major players like Dell, down to such mundane sources as Wal-Mart. As a bonus, you're likely to pay considerably less than for an equivalent Windows machine.

I still don't think this is for everybody, and I'll really have to pound on Open Office before I'm ready to sign-off on it. And like Mac users, Linux users are always going to find themselves facing programs they can't run, hardware they can't use, and things they can't do. It goes with the territory.

But it's at least now I see Linux as a viable option, if not for your primary computer, then maybe for your laptop or backup machine. It has many of the security advantages of a Mac, the openness (only better) of a Windows machine, and its cheap and friendly to any older hardware you may have laying around in the closet.

I'll continue to report our experiences, but if you're brave enough, and especially of you have a spare computer taking up storage space, go ahead, give it a try...

Monday, September 24, 2007

Gone but Not Forgotten



One sad thing about writing, as I often have, media tie-in novels, is that they have a tendency to last only as long as a given licensing agreement. That means that most of them have a very short shelf-life. In a year or two or three, they're out of print, and with very rare exceptions, they never come back. They're owned by whoever licensed the particular property. You don't get the rights back, and in general, the license owner has little or no reason to reprint the book.

Sometimes, that's a blessing, but other times, when you're especially pleased with a project, it's a very sad thing. For me, the latter was true of the two novels I wrote based on the since-canceled Marvel comic book, "Generation-X." They were fun to write, I was pleased with how they turned out, and I would have loved to have written more if I'd had the chance. Alas, I didn't, and now I never will.

But books have an after-life of their own, drifting through garage sales, used book-stores, eBay and the occasional library. Tonight (thanks to a Google Alert I have set up to search for my name) I was surprised to discover a new web review of the second of my Generation-X novels, Genogoths. (Follow the link, and you'll also find my extended back-story there on the writing of the two Marvel tie-in novels I did.)

Now, the reviewer didn't declare it the classic of the ages, but they did read the book and seemingly enjoyed it. Even better, they decided to share the experience with others (and incidentally, me). I'm not sure how a writer can ask for more, especially this late in the game.

Thanks to those of you out there keeping our lost books alive.

Friday, August 10, 2007

A REALLY Cold War


Having just passed the depressing age of 50 does have a few advantages. It gives one some perspective on history. It's perhaps even more profound when one, as I did, starts out, a fan of science fiction and space exploration.

Even as a child I was living outside the day-to-day, anticipating a future which, for the most part, has never arrived. We never got our rocket packs or flying cars, we haven't been to Mars, and in fact have yet to get back to the Moon (though there's at least some hope that it will happen in my lifetime, even if it isn't as clear which country is going to get there first).

As a whole though, it's sometimes strange how much is the same. We still mostly get places cars on concrete and asphalt roads, or in subsonic jet airliners that are, in terms of comfort, if not technology, probably a step backwards from a 1966 Boeing 707. The plug of a 1945 radio still fits in a modern wall socket, and while the bulbs are slowly changing, Thomas Edison would still have recognized most of the light-sockets they fit into.

Yes, there are computers and the Internet, cell phones, iPods and other techno-toys, but in general, history seems to march along in the same rut. Our current misadventures in the middle-east wouldn't be unfamiliar to anyone who lived through the Vietnam war or the Russian occupation of Afghanistan.

There are exceptions though. The fall of the Iron Curtain and the collapse of the Soviet Union being the most profound I can think of, events that clearly mark some kind of transition, that clearly state: things will never be the same again.

But for the most part, profound change is hard to come by. Most of all, while borders may squiggle and names on the map may mutate and shaft, the globe itself has remained the same. In fact, in looking into the future as a child, that was probably the last thing I ever expected to change. They don't call it the firmament for nothing.

But now the globe is changing. It's started, and it isn't about to stop. Of course, I'm talking about Global Warming, and not in the most obvious way, with the rising of sea-levels, the radical changes in coastlines, and the erasing of islands (and maybe much of Florida) that is likely to follow.

No, I'm talking about something which is changing much faster, something we folks who live in temperate regions don't normally think of as permanent at all: ice. Scientists have known for years that the arctic ice sheet is shrinking, and for places where land is normally locked in by sea ice, this is a profound change indeed. The mythical Northwest Passage for which early explorers of the Americas searched now exists, at least part of the time, and too soon, all the time. Compare it to a the appearance of a new ocean, or Atlantis reappearing above the waves.

But for those of us in the United States, this change has, so far, been fairly easy to ignore. Yes, one can point to Hurricane Katrina, but there's just enough scientific uncertainty about it's direct connection to global warming to allow for an easy state of denial. Same for the record-hot summers we've been having lately. Weather is, by definition, an uncertain business.

But maps are hard to deny, and for those to the north of us with each passing season they look out on a new world, one full of peril, and just possibly, opportunity. In such a situation, it shouldn't be unexpected that the balance of world power and tensions would shift. Still, I didn't see this one coming, and it's only taken a few weeks.

It started when Russia announced their intention to plant a flag under the ice cap on a submarine ridge extending out into the Arctic. Their intent was to lay claim to a until-now hidden region which may have untapped oil, gas, and other mineral reserves, made suddenly accessible by the melting ice cap. Russia claims the ridge is a natural extension of their homeland, and therefore should belong to them.

Some would dismiss the whole idea as silly, but several countries appear to be taking it very seriously. First, Canada, with designs on the same ridge, has announced its intentions to build a new deep-water port to service arctic patrol craft, to build new ships to use the port, and to beef up an existing paramilitary force called the Rangers (currently staffed mostly by part-time reservists) to defend their claims to the arctic region.

Then Denmark has started its own mapping expedition of the ridge, prepared to make their own claims under UN treaties.

Finally, surprisingly late to the party considering the current administration's close energy ties, the US is dispatching an ice-breaker to do a little mapping of their own off the coast of Alaska.

And just to raise the ante, Russia is now suddenly holding extensive war-games in the Arctic this week. Sabers, they are a rattling, and we're hardly getting started. With stunning speed, this is turning into a literal cold-war, and the long-term outcome is impossible to to predict.

Welcome to the future. We have passed through one of those portals of history, and nothing will ever be the same again. If you don't believe me, just look at the globe.