Duly keynoted

SAN FRANCISCO–I set a personal record for keynote livetweeting with the 3.5-hour production that opened Google’s I/O developer conference here on Wednesday morning. That was by far the longest tech-event keynote I’ve sat through, but nowhere near the strangest.

I:O logo onstageFor that, I might have to give the nod to Qualcomm CEO Paul Jacobs’ freakshow of a CES keynote this year that somehow included Steve Ballmer, Bishop Tutu, Guillermo del Toro and Big Bird. But I could also point to last year’s I/O keynote, capped off by a livestreamed skydive onto the Moscone West roof. Or what about the epic networking meltdowns of one of 2010′s two I/O keynotes?

The Microsoft keynotes that opened CES through 2011 were their own breed of weird, thanks to their history of random celebrity-guest appearances and technical meltdowns.

The keynotes Steve Jobs led for Apple were models of restraint in comparison. (I can’t speak to the live experience of those since his death, as I haven’t been gotten given a press pass to any of them.) Jobs spoke at a measured pace, the slides mostly consisted of white text on black backgrounds, supporting speakers didn’t come onstage to their own at-bat music, and the guests who didn’t work at Apple were almost always confined to executives at other tech firms cooperating with Apple on various projects–not random boldface names.

But the Steve Jobs And Apple Show made its own mistakes. The extended dissertation at Macworld NY in 2001 over how Apple’s PowerPC processors weren’t really slower than Intel chips was both legendarily dull and distinctly dodgy, given that Apple was already working on its subsequent switch to Intel. (Trivia: I think was also the one and only time a review of mine got favorably cited in an Apple keynote, when Jobs gave a shout-out to my iDVD review.) And was it really necessary to end each one by playing an ad for the new product not once but often twice?

I can’t think of too many other forms of creative output more in need of editing than the average tech-industry keynote. But if the people involved can’t do that, I have two lesser suggestions: Keep any slides with numbers on the screen a little longer, so we can jot them down correctly, and follow Google’s good example by providing power strips and Ethernet in at least the first rows of seats for the press.

About these ads

Your device can be too small and too thin (July 2012 CEA repost)

(Since a site redesign at the Consumer Electronics Association resulted in the posts I wrote for CEA’s Digital Dialogue blog vanishing, along with everything there older than last November, I’m reposting a few that I think still hold up. This one ran July 27, 2012; it’s on my mind again after two recent stays with relatives who had broadband Internet at home but no WiFi router connected to it.)

For well over a decade, I’ve had the same wish list for each new gadget: smaller, lighter and thinner than its predecessors. But lately, I wonder if I should be more careful about what I wish for.

too-thin laptopI still appreciate carrying around devices that weigh less and take up less space than earlier models—preferably while running longer on a charge. But some recent devices I’ve tested or purchased suggest the costs of being too thin or too small.

Consider the connections around the edges of many new laptops, including the MacBook Air I just bought, but also many Intel-based Ultrabook PCs. The thinnest among them often leave out wired Ethernet ports and standard HDMI video outputs, requiring users to pack adapters.

That’s not a huge tradeoff for video. If you expect to plug a laptop into a monitor or an HDTV, you’re foolish not to bring your own cable, and one with a micro-HDMI plug at one end will take up less space than a full-sized equivalent. But with networking, you’ll need to bring an adapter supported by your operating system or trust that Wi-Fi will always work, no matter how many other people jam the airwaves near you.

And as just about anybody who’s gone to CES or any other tech conference can testify, that rarely happens. Veterans of these events know to look for Ethernet, and some companies have taken note: Google won compliments for providing wired Internet access in the press seats at its I/O conference last month.

The race to build the thinnest laptop, as opposed to the lightest, doesn’t make much sense from a usability perspective. An added eighth of an inch in thickness won’t make a laptop any more awkward to operate or carry. It’s not a thick phone that will break the line of a suit when tucked into a pocket.

Smartphones risk a different sort of miniaturization malfunction. Since the 1990s, phones using the GSM standard have used compact SIM (subscriber identity module) cards to store account data. This has made it easy to move a number from one phone to another and, with an unlocked phone, switch temporarily or permanently to a new carrier.

That’s given GSM a serious advantage over the competing CDMA standard, which doesn’t require any such physical separation of an account and a phone. (Trivia: Some CDMA carriers have employed a SIM equivalent called an R-UIM  or removable user identity module, but not in the U.S.)

In recent years, the SIM scenario has gotten a little more complicated with the arrival of micro-SIM cards. But you can still use a micro-SIM in place of a standard card (technically a mini-SIM) if you pop it into an adapter or position it so its contacts align properly in the slot (I’ve done it, but it took a few tries). And you can cut down a SIM to micro-SIM size.

Now, however, the industry has certified a “nano-SIM” standard that is smaller still and slightly thinner. So you won’t be able to shoehorn a micro-SIM into a nano-SIM slot, and using a nano-SIM card in phones designed for bigger cards will require an adapter instead of just careful placement.

Whether saving .0037 cubic inches of space over the already tiny micro-SIM card (in context, .1 percent of the volume of an iPhone 4S, considerably less in the current crop of big-screen smartphones) is worth that complication seems to have gone unexplored. Would we be better off if everybody had standardized on micro-SIM and let designers find other ways to condense phone hardware? We’ll never know.

Manufacturing ever-smaller gadgets also imposes costs we may not notice until later on. You may find that you can’t upgrade the memory on a new laptop—a serious risk if an operating system upgrade requires more memory than the last release. Are we ready to foreclose on the idea of upgradable hardware?

Repairing a tablet or a computer can also move from tricky to difficult once its components get tightly-packed together. The same goes for recycling a defunct device—although if a manufacturer provides its own, easily accessible recycling service for those gadgets, I’ll give it a pass.

The risk in making this kind of complaint is sounding like a grumpy old man, desperately clinging to his trusty old Ethernet cable and SIM card as he stands in the way of progress and the laudable goal of making computers simple, worry-free appliances.

But at a certain point, standards friendliness, repairability and expandability should outrank shaving yet another fraction of an inch or an ounce off a product. That would leave plenty of other things companies can try to beat each other on. Did I mention battery life?

About marathons and for Boston

If you want to know what determination looks like, go to the finish line of a marathon.

Marathon finisher's medalI realized this in 1999, when I dragged myself out of bed shamefully late on a Sunday morning, walked over to the finish line of the Marine Corps Marathon and came home in awe of the agony and joy I’d seen on the faces of runners. Then in 2005 and 2007, I learned firsthand what it’s like to finish a marathon: triumphant, hands-in-the-air, yelling-out-loud elation, combined with a whole-body ache and stabbing pains in your legs that may lead you to crumple to the pavement after somebody hands you a finisher’s medal.

That moment caps months of training, possibly including waking up at 6 a.m. on weekends in July and August so you can run 13, 18 or 20 miles in the heat. Race day is, as people cheering along the course will remind you, your payday.

All this is to say that if anything could make the deliberate mass murder of innocents more vile, doing so at the finish line of a marathon would rank high on that list. The people who double-laced their running shoes this morning to make sure they wouldn’t come untied deserved that last sprint (or lurch), the final stomp on the timing mat at the finish line, and the giddy clutching of a shiny medal.

All of you who have clocked 26.2 miles, at some level you are my brothers and my sisters–so this feels like somebody went after my family.

It hurts further to see this happen to Boston. My brother lives just outside the city (and works only blocks from the finish line, but wisely chose to telecommute today); the Red Sox made a baseball fan out of me; I love visiting the place, and I really should come up with more excuses to go there on business. And at least two friends of mine have run the Boston Marathon. (My two MCM times were nowhere good enough to get me into Boston–but had I kept those paces today, I would have neared the finish line at about the worst possible time.)

Boston and runners, my heart aches for you tonight. But we will get through this.

Qualms Over QAM (2012 CEA re-post)

(Since a site redesign at the Consumer Electronics Association resulted in the posts I wrote for CEA’s Digital Dialogue blog vanishing, along with everything there older than last November, I’m reposting a few that I think still hold up or shed light on current issues. This one ran on Feb. 14, 2012;  the AllVid effort I mentioned at the end has gone nowhere since, but in October, the Federal Communications Commission voted to allow QAM encryption–with results that I’ll be discussing in this weekend’s USA Today column.)

This month’s telecom-policy squabble covers a TV technology that nobody seems to love–if they even know it exists.

The system in question goes by the name QAM, short for “quadrature amplitude modulation,” and it’s the only way to tune into digital cable without a box. But while “cable-ready” sets dealt fairly well with even premium channels in the mid 1990s, QAM’s horizons are far more limited.

Coax cableYou can’t count on QAM providing more than the “basic tier” of local broadcast stations plus public, educational and government channels. Forget ESPN or even CNN; to get those without a cable box, you need a CableCard-compliant device–which in practice means either a TiVo digital video recorder or one of a few add-on tuners for computers.

But it’s worse than that: As readers have testified and I’ve seen myself, QAM reception often presents a puzzling picture of your cable choices. Channels can appear under seemingly random numbers–and then move to new ones or disappear outright.

So the proposal now before the Federal Communications Commission to allow cable operators to encrypt QAM signals on all-digital networks–simplifying their systems while cutting off existing QAM hardware–might not seem like anything worth fussing over.

And yet for a small minority of users, QAM does work. Some use it on second or third sets (PDF); some resorted to basic-tier cable after failing to get adequate over-the-air digital-TV reception; some employ it to use computers as digital video recorders. And these subscribers don’t want it to go away.

How many people are we talking about? The Web-media-receiver vendor Boxee says that 40 percent of buyers of its new Boxee Live TV device use QAM to receive cable TV through that add-on. You could dismiss that as a figment of a small sample size; that $49 add-on has only been on sale since January. But a more established computer-video vendor, Hauppauge Computer Works, also cited 40 percent QAM usage (PDF) among buyers of its PC peripherals.

The Consumer Electronics Association has no stats for this segment of the market.

CEA has joined those manufacturers in their opposition to QAM encryption, writing in a November filing (PDF) that the FCC should decline this request unless it also moves forward on other, long-standing proposals to open up the market for TV hardware (more on that in a moment).

The cable companies’ arguments, as related over a call Friday with representatives of the National Cable & Telecommunications Association, fall into three categories:

• Cable operators’ own figures suggest that almost nobody relies on QAM. Cablevision, which obtained a waiver from the FCC to start encrypting QAM after converting to all-digital service in New York, N.Y., reported that “less than 0.1 percent of subscribers” (PDF) requested a free set-top box or CableCard to decode it.

• Encryption will allow remote activation and deactivation, without sending a technician on a truck to somebody’s house. (NCTA realizes that people don’t like sitting through four-hour service windows.)

• Encryption will also stop people from tuning into basic-tier cable without paying. RCN, among other cable operators, reports (PDF) this is a growing problem among Internet-only subscribers.

It’s important to note that the the cable operators, while maybe not everyone’s favorite companies, have been way ahead of satellite vendors in the interoperability game. DirecTV users who wanted to plug in a TiVo could only wait for that service to ship its own “DirecTiVo” model; that recently arrived, years late, to complaints over its aged interface.

Meanwhile, CableCard finally seems to work as advertised–even if that’s happened too late for some pioneering CableCard vendors. Once-prominent TiVo rival Moxi Digital gave up the fight two weeks ago when its new owner, ARRIS Group, announced that it would only sell through cable operators.

There’s been a proposal afoot, against opposition from cable, to set a comprehensive pay-TV standard called “AllVid” that would work not just for cable but also satellite and fiber-optic services. It would allow every screen in a home network to tie into a simple gateway adapter–the video equivalent of the wireless router that links a cable modem and a laptop.

That’s what CEA has been asking for in return for giving up clear QAM. Boxee could also live with this tradeoff, said spokesman Andrew Kippen; Hauppauge CEO Ken Plotkin, however, was not to ready to make that deal.

Me, I think I could live with that bargain–if it included an assurance that current QAM users who will have to tolerate a new box and remote control won’t have to pay extra for them. (If encrypting QAM harms so few people and yields as many benefits as cable operators say, they should be able to afford subsidizing that hardware.)

But this is an easy thing for me to say, since I switched to over-the-air and Internet broadcasts years ago. If you pay for cable today, I’d rather know your opinion: Would you trade simple reception of entry-level cable today for easy access to a full lineup of channels a few years from now?

Overlooked E-Book Chapter: DRM Makes Monopolies (2012 CEA repost)

(Since a site redesign at the Consumer Electronics Association resulted in the posts I wrote for CEA’s Digital Dialogue blog vanishing, along with everything there older than last November, I’m reposting a few that I think still hold up. This one ran on April 17, 2012; since then, sci-fi publisher Tor Books–a subsidiary of the Macmillan publishing conglomerate–has gone DRM-free, but most of the industry has yet to take that step.)

Even if you’ve been following the e-books story for the past five years, it can be hard to define the heroes and villains of that plot.

First Amazon was the innovator, liberating us from paper with its Kindle. Then Apple was going to upend things with the iPad’s iBooks app and store. Now the Department of Justice says that the real problem is an unholy union of the publishers and Apple.

E-book reader appsIn an antitrust lawsuit announced last Wednesday, the DoJ charged Hachette Book Group, HarperCollins Publishers, Simon & Schuster, Macmillan, Penguin Group and Apple with conspiring to fix prices, to the disadvantage of consumers and Amazon.

The first three publishers have already agreed to a settlement that will block “most-favored nation” clauses that prevent e-book stores from discounting titles while allowing them to place other limits on the sale of their work. Meanwhile, Macmillan, Penguin and Apple continue to fight the suit.

It’s an immensely complicated issue, colored to a large degree by who you think is more evil. Is the problem the big publishers targeted by the DoJ’s suit, who allegedly colluded over dinners in expensive Manhattan restaurants? Or is it the gigantic Seattle retailer, which both controls a huge share of e-book sales and has been getting into the publishing business itself?

(A CEA press release posits a third foe, quoting association president Gary Shapiro calling the lawsuit “another sad milestone in our government’s war on American companies.”)

But the basic issue at stake here is not complex: ensuring vigorous competition in e-books that eliminates the need for court battles and consent decrees. And in that context, you can’t ignore how publishers have not just given Amazon a tool to build a monopoly but required its use.

This is the “digital rights management” restrictions required by publishers on e-book titles sold through all of the major online outlets–not just Amazon’s Kindle Store but also Barnes & Noble’s Nook store and Apple’s iBookstore.

DRM is supposed to stop unauthorized copying and sharing by making a copyrighted work playable, readable or visible only on authorized products. It’s not always a huge annoyance: DVDs and Blu-ray discs employ standardized–if easily circumvented–DRM that doesn’t limit you to player hardware or software specifically approved by a movie studio.

But in the world of digital downloads, DRM usually locks the “buyer” of a DRMed item into using only one vendor’s hardware or software.

(The scare quotes are necessary because the license agreements for many DRMed items stipulate that you don’t actually own those downloads.)

If you want to keep your future hardware and software options open, this favors doing business with the e-book store that offers the most DRM-compliant reading options.

That store, by a hardcover-thick margin, is Amazon. Beyond its growing family of Kindle reader devices, including last year’s Kindle Fire tablet, it also ships reader apps for Windows, Mac OS X, Linux (via a “Cloud Reader” Web app) iOS, Android, Windows Phone 7, BlackBerry and even HP’s now-abandoned webOS.

Barnes & Noble, by contrast, only provides Nook reader apps for iOS, Android, Windows and OS X. And Apple limits iBooks to its iOS devices.

Considering that evidence, where do you think somebody ought to shop?

So long as DRM stays part of the plot, every Kindle reader sold, every Kindle app installed and every Kindle title purchased will strengthen Amazon’s hand.

DRM can’t solve this problem, any more than any form of DRM tolerable to home users can abolish copyright infringement. But ditching it would erase the equation. If you could buy an e-book in a standard format that, like an MP3 music file, would be playable on current and imaginable future hardware, it wouldn’t matter which store sold it. There would be no lock-in; each sale would would not weigh so heavily on the next.

(As I wrote last spring, not having to worry about DRM-induced obsolescence would also vastly increase the odds of me buying e-books at all.)

The music industry figured this out years ago. Giving up on the DRM dream enabled a thriving competition between Apple, Amazon and other vendors of digital downloads, with no lock-in beyond the relative difficulty of syncing music from iTunes to a non-Apple device.

Other observers of the e-book business have been making the same call on personal blogs and on tech-news sites. One publisher, Hachette, may even be paying attention, as PaidContent reporter Laura Hazard Owen wrote last month.

But in much traditional-media coverage of digital content, DRM remains the lock that dare not speak its name. You can read a thousand-word piece about the slow market for movie downloads that notes a “lack of interoperability” without ever explaining why–or even using that three-letter abbreviation. Many of last week’s stories about Amazon, Apple and book publishers miss this point just as badly. And if we can’t properly identify this issue, we certainly can’t fix it.

DMCA exemptions: requesting permission to innovate (2011 CEA repost)

(Since a site redesign at the Consumer Electronics Association resulted in the posts I wrote for CEA’s Digital Dialogue blog vanishing, along with everything there older than last November, I’m reposting a few that I think still hold up. This one ran Dec. 16, 2011; it may help explain where the last few months of headlines about phone unlocking came from.)

One of the stranger rituals of U.S. tech policy is now unfolding in Washington: the triennial reassessment of the Digital Millennium Copyright Act’s “anti-circumvention” rules.

In this exercise, the Librarian of Congress considers granting exemptions to the DMCA’s ban on picking digital or electronic locks that control access to copyrighted works. The DMCA mandates this review because of the possibility–in retrospect, certainty–of companies abusing their immunity from customer interference with “digital rights management” systems to limit non-infringing uses.

DMCA exemption rulemakingYou may prefer to call this a “requesting permission to innovate” ritual.

In four earlier rounds of exemption proceedings–in 200020032006 and last year–Librarian James H. Billington has inconsistently expanded the range of DMCA exemptions, sometimes taking away earlier permissions.

He legalized hacking into Web-filtering software to inspect lists of blocked sites the first two times but didn’t renew that in 2006. The exemption granted in 2000 for defeating broken DRM mechanisms that wrongly deny access was then narrowed to a loophole for breaking obsolete or malfunctioning “dongle” hardware keys. (A related exemption, covering systems that require presenting an original copy of a program or game in a storage format that has become obsolete, arrived in 2003 but was not renewed in 2010.)

E-book customers won the right in 2003 to hack their DRM if it prevented the use of screen-reader accessibility software and have kept it since, but no equivalent accessibility exemption has been granted for movie viewers. And yet in 2010, the Librarian legalized ripping “protected” DVDs for fair-use criticism and commentary purposes, something still not allowed for DRMed e-books or music.

2006′s exemptions let you unlock a phone to use on a competing network, but 2010′s narrowed that to used phones. But last year’s proceeding also granted the right to jailbreak a phone to install the software of your choice–a big development for iPhone users.

Perhaps unsurprisingly, many of the 20 comments submitted in this year’s proceeding focus on preserving prior gains or ironing out inconsistencies.

For example, a group called the Library Copyright Alliance only wants to renew 2010′s DVD-ripping exemption, while the University of Michigan’s library seeks to have its protected class of students widened beyond those in “film and media studies.”

(Those links and all that follow point to PDF files.)

Public Knowledge wants to see the current DVD rule extended to cover “space shifting” to other formats, noting the increasing number of laptops without DVD drives.

A coalition of Telecommunications for the Deaf and Hard of Hearing, Gallaudet University and the Participatory Culture Foundation propose granting a broader exemption to make movie downloads, streams and discs accessible to those with hearing or sight impairments.

A group led by the International Documentary Association proposes to expand the same provision to cover Blu-ray discs and movie downloads and streams so that future filmmakers can incorporate fair-use excerpts in documentary or fictional works. A set of professors at the University of Pennsylvania and elsewhere make the same request for educational use and are echoed by the University of Rhode Island’s Media Education Lab.

The American Council of the Blind and the American Foundation for the Blind, meanwhile, want to maintain an exemption for making e-books accessible to readers with limited vision. The Open Book Alliance wants another for removing DRM from books that are already in the public domain.

Mobile devices figure in over a quarter of these submissions. Small wireless firms MetroPCS CommunicationsYoughiogheny Communications and a trade group called RCA – the Competitive Carriers Association all want to renew and expand 2010′s phone-unlocking exemption to cover mobile devices in general, not just phones. Consumers Union concurs.

The Software Freedom Law Center also favors allowing device owners to install the operating system of their choice. It also wants to permit desktop users to bypass any mandatory app stores–although neither Windows nor Mac OS X impose that restriction today.

The Electronic Frontier Foundation sent in an all-of-the-above brief backing exemptions for jailbreaking phones, tablets and video-game consoles and another set for unlocking DVDs, downloads and streams to extract fair-use clips.

Four submissions from individuals request blanket waivers on circumvention for personal use; a fifth seeks one for the narrow category of DRMed e-books in the Mobipocket format Amazon no longer supports on its Kindle readers.

We’ll have to wait until sometime in February to see which of these requests get a favorable hearing, or if any of 2010′s exemptions will disappear. That’s plenty of time to contemplate a broader question: If a far-reaching provision of a law carries such a high risk of collateral damage that an unelected official must drill holes into it every three years–and those holes seem to get bigger over time–shouldn’t we think about rebooting that rule?

That war I bought into 10 years ago

A decade ago, I was staying up late to watch my country invade another. I had a personal investment in the war I saw unfolding on TV and on the Web: One of my cousins was a corporal with the Marines, and his unit was crossing the border into Iraq. And I had been persuaded that we were doing the right thing.

Post Baghdad front pageThe reporting I’d seen in my newspaper and others told me that we had probable cause of Iraqi chemical, biological and nuclear weapons efforts. The front page of March 20th’s edition of the Post treated them as givens.

Sure, I hadn’t found President Bush to be the most convincing advocate. But Colin Powell knew of what he spoke, right? And I, like others, thought British prime minister Tony Blair had made an eloquent case for the grim necessity of war.

Early on, it looked like we’d be proved correct. Only weeks after the start of the war, Baghdad fell; I kept that day’s A section of the Post as a souvenir.

Then everything got so much more complicated over weeks, months and years. My cousin came home safe (as did his sister, who followed him into the USMC and then Iraq), but thousands of other Americans did not. The day-one gung-ho reaction on newspaper front pages looks like a cultural fossil now.

I’m not writing this to unpack the last 10 years of U.S. policy in the Mideast. You can overdose on that elsewhere. It’s just an appropriate day to admit that I got spun into believing things that weren’t so–and so did too many of the journalists who wrote the stories that had helped convince me.

Yet another airline prepares to pull into the hangar in the sky

With yesterday’s announcement of a planned merger between US Airways and American Airlines, one more airline I’ve flown will vanish from the skies. Well, not its planes or people, but its name, livery and two-character code, and hopefully its call sign too: It would be tasteless to ditch AA’s “AMERICAN” for US’s America West-derived “CACTUS.”

Pan Am boarding passThe list of defunct U.S. and foreign airlines–excluding regional carriers and those from childhood that I don’t remember–that have transported me from one place to another is longer than I’d thought. I’m not sure if that demonstrates the crummy economics of the airline business or merely my own advancing age.

  • Aloha: We flew them to and from Maui for a friend’s wedding several years ago. Maui is an excellent place to go to a friend’s wedding.
  • America West: My chosen conveyance to and from CES for a year or two. I don’t miss their hideous livery at all.
  • ATA: My wife and I took this discount carrier to Chicago and San Francisco a couple of times.
  • Braniff International: I was on them a few years with my parents in the ’70s or ’80s. Their colorful paint jobs are still missed.
  • China Southwest: Flew me from Chengdu to Lhasa, Tibet and back on a memorable, two-and-a-half-week-long vacation in 1998.
  • Continental: The first airline I reached elite frequent-flyer status on; some of those miles went towards upgrading our honeymoon flights (they took great care of us), and some are still in my United account.
  • Eastern: Flew them up and down the East Coast a few times growing up.
  • National: This short-lived airline got me from San Francisco to Las Vegas–horribly late–for one Macworld-plus-CES trip.
  • Northwest: They got me to Tokyo and Hong Kong on that 1998 but couldn’t get me home, courtesy of a strike that resulted in my getting rebooked on United a day later. Did I complain about having to spend an extra day in Hong Kong? No.
  • Pan Am: The one I miss most of all, as do all self-respecting aviation dorks.
  • PeoplExpress: Not “People’s Express,” damnit. I learned years later that their dense, single-class configurations had earned them the nickname “PeopleCompress.”
  • TWA: I think this was the first airfare the Post paid on my behalf, courtesy of the paper sending me to cover the first E3 video-game trade show in L.A. in 1995.

If you have anything you’d like to say about the departed, the comments are all yours.

Ad astra per aspera

Ten years ago today, my friend Doug interrupted a lazy Saturday morning to call with an urgent question: Do you have the TV on?

STS-107 memorialThat’s when I learned that the space shuttle Columbia should have landed in Florida but never would. I spent the rest of the day obsessively watching the news and thinking “I hate to see the good guys lose one.”

(I’m embarrassed that I’d forgotten about Columbia’s scheduled return before that call, but more so that I didn’t head into the newsroom to help in some way that Saturday.)

When Challenger disintegrated, I was all of 15 years old, and it shook me to see the people I had thought capable of engineering miracles stumble so badly. But it was comforting to think that NASA–that we–had learned and would never again think that “this worked every other time” outweighs “here’s why it might not.”

We didn’t learn enough, because we should have seen the tragedy of STS-107 coming. Only two launches after Challenger, Atlantis came home with hundreds of tiles scarred by insulation flying off after liftoff. Fourteen years later, that risk caught up with Columbia.

Columbia was the shuttle my 10-year-old self, entranced and exhilarated, woke up early to watch launch in 1981, and the one I looked forward to seeing in the Air and Space Museum someday. Instead, the shuttle and astronauts Michael Anderson, David Brown, Kalpana Chawla, Laurel Clark, Rick Husband, William McCool, and Ilan Ramon were gone.

When I made my long-awaited pilgrimage to the Kennedy Space Center two years ago, I was struck by the enormous STS-107 insignia hanging inside the Vehicle Assembly Building–a silent reminder to stay skeptical in the face of apparent success.

We honor the crew of Columbia as well as Challenger’s Greg Jarvis, Christa McAuliffe, Ron McNair, Ellison Onizuka, Judith Resnik, Dick Scobee and Michael Smith–and before them, Apollo 1′s Roger Chaffee, Gus Grissom and Ed White, Soyuz 1 cosmonaut Vladimir Komarov and Soyuz 11′s Georgi Dobrovolski, Viktor Patsayev and Vladislav Volkov–if we remember that lesson as we continue their worthy endeavor.

“This is not the day”

Not long after learning of yesterday’s horrible news of a mass shooting, I thought about the post I’d started writing after earlier horrible news of a mass shooting, then finished after still other horrible news of a mass shooting. I referenced it in a tweet, and was promptly called out by a couple of people who objected, strenuously, to bringing up anything with a whiff of politics. Why?

This is not the day.

I should have expected replies like that. But why? What is the logic of that reflexive responseeven from people who don’t support loosening gun regulations–every time some sad individual takes a gun and kills a dozen or more of his fellow human beings?

I am not talking about self-serving commentary by those looking to cash in politically or financially. Think of Mitt Romney grotesquely distorting recent American public diplomacy in the Middle East hours after the murder of Ambassador Chris Stevens or, on a lesser level of offensiveness, Sen. Chuck Schumer (D.-N.Y.) demanding publicly that Apple “set the record straight” about the reception of the iPhone 4′s antenna or all of those foolish publicists who think calling out a recent tragedy in a PR pitch will get reporters to cover the client’s product.

No, I am speaking of citizens who want to know what went wrong and what we could have done to prevent it. What other reaction could we possibly have to an atrocity like the murder of 20 children? (As the father of a two-year-old, I was almost shaking with rage at one point yesterday.) Wondering what we could have done differently is, as Maggie Koerth-Baker noted astutely, is part of the bargaining stage of grief.

This is what we’ve done after a hurricane floods subway tunnels and shuts out the lights across much of New York City, a highway bridge collapses, a space shuttle breaks up on reentry, and hijackers fly airplanes into buildings. We would be less than functioning, inquisitive human beings if we did not ask if we could have done anything different, even on The Day.

That may “politicize the tragedy.” But so does attempting to short-circuit any discussion about our options because This Is Not The Day. And in a democracy, politics is how we have to solve some of our biggest problems.

So to those of you who want to use your First Amendment rights to defend your Second Amendment rights the next time, please find another talking point. Because this one does not help your cause. And this discussion could use your reasoned input, not your denial.