I'm writing this column from a hospital, specifically, its Critical Care Unit (CCU). They used to call these intensive care units, or ICUs. Before unit became current, they were wards. All the name changing causes confusion. I wonder if it's enough to cost lives.
It's conceivable. Two doors down, they had a Code Blue this morning. Machines were wheeled in. Staffers hurried around, carrying clear tubes and bags of fluid. A chaplain paced in the hall. Groups of family members cried on each other's shoulders. They deal with life or death in here. A hospice worker a few minutes ago told me “a lot of the people in there are wheeled out feet first.”
Fortunately for me, I'm not a patient here. Unfortunately for my mother, she is, thanks to complications following a gallstone removal procedure. So I've been hanging around as a visitor for most of the past week. Every once in a while, I go over to the counter by one of the nursing stations, where a Microsoft Windows 2000 Professional logo floats on a black screen above a black keyboard and a mouse. When I move the mouse, the screen comes to life, offering me a choice between Staff Login and Internet Explorer. After clicking on Explorer, I surf the Net until it crashes on some site, bringing the rest of the machine down with it.
I asked a nurse yesterday if this kind of crash also happens when the systems are running the hospital's own applications, which mostly are used to access patient records and recent lab results. “Those things are down all the time”, she said. “We have all kinds of problems with them.” After hearing her response, I wondered, “what are costs—in time, money and human lives—to running hospital computers on a crashy operating system?”
Three weeks now have passed between the last sentence and this one. Several days after I wrote everything above, my mother's condition improved to the point where she could be moved out of the CCU. She had fought hard against pain so extreme that she needed frequent doses of morphine, which were shot into one of the many stretches of tubing that ran in and out of her frail, 90-year-old body. But she was tough and willful; her mind still was strong and amazingly lucid, especially considering all the chemical insults it endured.
“Are you gonna make it, Mom?” I asked. She said yes and told me to head back home to California. That night, best they can figure, she had a stroke. Two days later her cardiologist came by, surprised to find her there. He hadn't been told she was in the hospital and therefore hadn't been consulted about her medications, which he carefully had prescribed and monitored over the last ten years, ever since she had been diagnosed with congestive heart failure. The next day, she died.
It's easy to second-guess everything at times like this. Any one of us—doctors, nurses, relatives—could have made sure to involve the cardiologist. And, as many doctors and nurses have told us (some of them members of our own family), Mom's odds were long at best from the moment the original procedure went poorly, which often happens with elderly patients. She knew the risks going in. She also lived a full and happy life. Before she slipped out of consciousness, she told my sister that she had no unfinished business and was ready to go. Her last word was love. She passed peacefully and without pain.
So I have no complaints about her treatment, which was excellent. I also know that every botched procedure, every course of treatment that fails to reach the ideal outcome—and, let's admit it, there are many—is a learning experience. One thing I would like hospitals to learn is how to get along without crashy software.
My mother died in late August 2003, during a time when the Blaster/Lovsan worm was infecting and spreading among countless Windows computers. A few days later, on “The Linux Show” (where I'm a weekly regular), Bruce Sterling told us there is no overestimating the level of hatred for Microsoft that the latest round of viruses is causing, especially outside the US. He recently had returned from Europe, where he found large cadres of locals determined to move beyond dependency on Microsoft. Bruce also wondered out loud whether there would be any kind of software business at all when “open-source nirvana” finally was achieved. Here's how he put the situation in a Wired piece titled “Freedom's Dark Side: The iron fist, the invisible hand, and the battle for the soul of open source” (www.wired.com/wired/archive/11.09/view.html?pg=4):
Logically—indeed, free-software geeks are the most logical hippies in the whole wide world—the revolution is at hand. Why should anybody pay for software? What do you get for your money besides shrink-wrap licenses, potential lawsuits, DRM cuffs around both wrists, and a cloud of viruses? “Property relations” are blocking social and technical progress. Secure computing and digital rights management are coercive regimes that would make George Orwell blush. The free market is a tissue of political fiction as brittle as an Eastern European regime. With open source code on tap, the software trade will collapse under its own weight....
From Redmond or Cupertino, it may seem decadent that an elitist scrum of hairy cyber-Euristas would style itself a cultural avant-garde. But consider the track record. In 1989, European civil society tore the guts out of Communism. When the Europeans won the Cold War, they got a bonus the US never did: zillions of eager former Commies. For these New Europe types, open source is a great, glittering step up from the vile product they're used to: broken-open source software, as in pirated CDs sold off blankets at flea markets.
The denizens of Open Cultures want their connected collectivism to liberate the world from regulations, markets, and intellectual property. But what if victory only clears the way for corruption of their beloved culture?...I have to wonder what dark passions and ancient evils have been held in check by the grim totalitarianism of the profit motive. We may yet find out.
Clearly, Microsoft's operating system and the PC productivity software business are threatened, or Microsoft wouldn't repeat “Linux” and “threat” so often in the same sentences. But it's a huge mistake to assume they are the only software businesses worthy of the label. What about that hospital software? What about the database, corporate accounting, customer resource management and transactional computing stuff that companies all over the world use to run their businesses? Do these all have to run on Windows? Do even a few? Look at Oracle, which abandoned its formerly nonpartisan orientation to operating systems and embraced Linux with a whole heart and a fattening wallet. Last I looked, Oracle still was growing like a weed and making billions of dollars on margins they've kept north of 75%. Look at Amazon and Orbitz, both of which run everything they can on Linux.
These companies, of course, are the obvious ones. How about the countless small- and medium-sized businesses and the categories they occupy? I'm talking here about stuff that stays way below the radar, because what they do isn't sexy or leading edge, even if they're the folks whose listings fatten our yellow pages.
Take, for example, the junkyard business. Last week, I was talking with my friend, Allan Harrell, in Phoenix, who has ties with body shop, body parts and junkyard businesses, even though his main job is keeping small business networks and computer systems up and running. After telling me how full his plate has become, thanks to all the viruses infecting Windows machines in his care, he mentioned FastParts, Inc. (fastpartsinc.com), the country's second largest supplier of computerized inventory systems for junkyards.
Intrigued, I got Jim Mangham and Wayne Leland on the phone to tell me about it. Jim owns the company, and Wayne is the “lead programmer systems guy”. They have a staff of seven and a customer base of 750. Wayne said the company has been using Linux for six or seven years; they like being able to hack the kernel and otherwise customize systems to do what they want.
FastParts sells a service that's delivered with a turnkey system in a white box. Customers view and operate it in a terminal window on whatever system (usually Windows) they happen to be using, including dumb terminals (Wyse, Sherwood) that FastParts is happy to provide.
FastParts is a personal service business, delivering and installing the systems themselves, including the modem phone connection that lets the company dial into a machine, do diagnostics and fix problems. Customers also call in through the system to look for car parts on FastParts' central system. “Many of our customers are too far out in the sticks to get a high-speed Internet connection”, Wayne says. “We have one guy on the road full-time, just installing.”
How do they compete? “Reliability, pricing and support”, Wayne says. “Out of all our competitors, where we get 'em is with support. Most of the other ones have modern telephone systems with all these menu choices you have to go through, and most of our customers do not like that. They want to get a real person when the phone rings. With us they get that.”
To me, that's the real story of Linux and open source. It's the ability of any expert in any field that requires any computerization at all to build a business that delivers what customers want—thanks to underlying software building materials that are free.
One of these days we'll all understand what's been obvious for years to guys like Wayne Leland: that free software is the best bedrock for a healthy and free computing marketplace—regardless of whether it threatens prevailing monopolies.
Doc Searls is senior editor of Linux Journal.
Doc Searls is Senior Editor of Linux Journal
- One Port to Rule Them All!
- Privacy Is Personal
- PHP for Non-Developers
- Secure Server Deployments in Hostile Territory
- Linux Kernel 4.1 Released
- Django Templates
- July 2015 Issue of Linux Journal: Mobile
- A Code Boot Camp for Underprivileged Kids
- Practical Books for the Most Technical People on the Planet
- Attack of the Drones