The Other Shoe
Before the Internet, networks were private affairs. You bought them from Novell or Microsoft or IBM. More accurately, you bought a set of network services you could obtain only from certain companies. You got file and print from Novell or Microsoft, messaging from Lotus, security from IBM and so on. None of those services would cooperate with those same services from other companies. That's not how “The System” worked. Every vendor wanted to be your only vendor—never mind that no vendor could provide anything close to all the services you needed.
The Internet broke that system by taking several network services and putting their protocols (i.e., HTTP for Web, SMTP for messaging, FTP for file transport and others) in the public domain, running on top of the equally public network protocols of TCP/IP. This gave us a high degree of interoperability for the first time. The Internet still does not perform many services at all, or performs them incompletely, so it did not put Novell and Microsoft out of business. The “Old Guys” still perform very well, but the Internet gave their businesses a whole new context—a public one. In a blink, their whole world changed, along with everyone else's.
It's still changing. When the Internet finishes settling in, almost everything in communications will depend on it, from embedded controllers to Palm Pilots to the entire phone system. But perhaps the Internet was just the sound of one shoe dropping—and the other shoe is Linux.
Linux seems to have the same calling: something free for everybody. The Internet seems to be its natural companion. Already the vast majority of web pages are served by Apache, running mostly on Linux systems. Are web services an enterprise beachhead for Linux? Or are they just a vertical application with little leverage?
Is there a big-time business model for any Linux vendor, besides attracting expensive investment bets from Microsoft OEMs and partners looking for alternatives? Are there other possibilities, all as radical and sensible as Linux itself?
How hard is it to imagine Linux kernels as the most basic building blocks of networked life? For Linux geeks, it goes without saying. For the rest of us it's a big stretch, especially when Linux still looks like a Swiss watch delivered in 400 separate parts. But so was imagining a networked world that wasn't a medieval mess of warring states dominated by the Empire of Microsoft, the Duchy of Novell and the Blue Kingdom of IBM.
We're still less than halfway through the shift from personal to social computing. Most households do not have PCs, and most that do are not connected to the Net. According to design critic and user advocate Don Norman, the two basic reasons for this are: computers are too complicated for many people, and the Net still lacks a plug-and-run infrastructure. He lays out a short-form prognosis in the title of his latest book, The Invisible Computer: Why Good Products Can Fail, the Personal Computer Is So Complex, and Information Appliances Are the Solution.
People are social. Telephony is equally social, because it lets people converse over simple appliances (incomprehensible cell phones and PBXes notwithstanding). Computing is social too, but only for a minority. There is still no computing appliance that's as social as the telephone. Will Linux deliver it?
I suggest that the first social computing appliance—let's call it the first SC—will cost less than $400, look friendlier than an iMac, get on the Internet with the ease of a phone call, and produce Microsoft Office-compatible files for those who want to use simple productivity applications.
Well, a prototype of that appliance can be built right now by slapping just about any Linux, any desktop and any office suite onto a commodity PC too slow for Windows 98, and a Windows newbie will probably know how to use it.
On the server side, the appliances are already here. The Cobalt Qube 2 is a seven-inch blue cube that anyone with an IP address can put on the Web in minutes and control easily over a browser. It runs Apache on Linux, but Cobalt doesn't mention that fact anywhere other than its data sheets. Why? Because it's an appliance. What's in it matters no more than what makes heat in a steam iron. All that matters is that it works.
Right now, the companies moving in the appliance direction are what economists call “fast followers.” Microsoft was once a fast follower of Apple, which is why Windows is a MacOS knockoff. Now Corel, KDE, Star Division and GNOME are fast followers of Microsoft, which is why their goods are not only effective clones, but in some cases (most notably Corel's) significantly improve on what they copy. Are they headed in the right direction? Not if they don't follow the user even more obsessively than they follow Microsoft. Don Norman says:
The successful family of information appliances will be built around the people who use them and the tasks to be performed. Products in the world of information technology have suffered far too long under the existing technology-centered designs... Today it is the individual who must conform to the needs of technology. It is time to make technology conform to the needs of people.
Currently, Linux requires far more compliance than Windows or Macintosh. Can that change? Only if some folks in the Linux community start to remember “the rest of us” abandoned by Apple fifteen years ago. If they do, the other shoe is sure to drop—big time.
Doc Searls is Senior Editor of Linux Journal
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Non-Linux FOSS: libnotify, OS X Style
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- RSS Feeds
- Reply to comment | Linux Journal
45 min 22 sec ago
- Reply to comment | Linux Journal
4 hours 45 min ago
- Yeah, user namespaces are
6 hours 1 min ago
- Cari Uang
9 hours 32 min ago
- user namespaces
12 hours 26 min ago
12 hours 51 min ago
- One advantage with VMs
15 hours 20 min ago
- about info
15 hours 53 min ago
15 hours 54 min ago
15 hours 55 min ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?