Leaving the Land of the Giants
The next revolution will be personal. Just like the last three were.
The cover of the December 1st–7th 2012 issue of The Economist shows four giant squid battling each other (http://www.economist.com/printedition/2012-12-01). The headline reads, "Survival of the biggest: The internet's warring giants". The squid are Amazon, Apple, Facebook and Google. Inside, the story is filed under "Briefing: Technology giants at war". The headline below the title graphic reads, "Another game of thrones" (http://www.economist.com/news/21567361-google-apple-facebook-and-amazon-are-each-others-throats-all-sorts-ways-another-game). The opening slug line reads "Google, Apple, Facebook and Amazon are at each other's throats in all sorts of ways." (Raising the metaphor count to three.)
Now here's the question: Is that all that's going on? Is it not possible that, in five, ten or twenty years we'll realize that the action that mattered in the early twenty-teens was happening in the rest of the ocean, and not just among the mollusks with the biggest tentacles?
War stories are always interesting, and very easy to tell because the format is formulaic. Remember Linux vs. Microsoft, personalized as Linus vs. Bill? Never mind that Linux as a server OS worked from the start with countless millions (or even billions) of Windows clients. Or that both Linus and Bill had other fish to fry from the start. But personalization is cheap and easy, and there was enough antipathy on both sides to stoke the story-telling fires, so that's what we got. Thus, today we might regard Linux as a winner and Microsoft as a loser (or at least trending in that direction). The facts behind (or ignored by) the stories mostly say that both entities have succeeded or failed largely on their own merits.
Here's a story that illustrates how stories can both lead and mislead.
The time frame was the late 1980s and early 1990s, and the "war" was between CISC (Complex Instruction Set Computing, http://en.wikipedia.org/wiki/Complex_instruction_set_computing) and RISC (Reduced Instruction Set Computing, http://en.wikipedia.org/wiki/Reduced_instruction_set_computing). The popular CPUs at the time were CISC, and the big two CISC competitors were Intel's x86 and Motorola's 68000. Intel was winning that one, so Motorola and other chip makers pushed RISC as the Next Big Thing. Motorola had an early RISC lead with the 88000 (before later pivoting to the PowerPC).
At the time, I was working with Sun Microsystems and its allies on SPARC, Sun's RISC design, which was implemented in various ways by a raft of chip makers, including Texas Instruments, Fujitsu and Cypress Semiconductor. In spite of Sun's heft in the marketplace, we had trouble getting attention for SPARC with the tech pubs, because they tended to see everything as an Intel vs. Motorola fight. We felt we couldn't challenge either one of those guys head-on, even if SPARC was superior on technical grounds (which Sun and its partners believed). So we decided the best strategy was for SPARC to pick a fight with another RISC upstart called MIPS.
This was pure bait for the pubs, which came over to this new fight to see what was up. I think we caught MIPS off guard at first, but it defended itself well and ended up selling years later for hundreds of $millions to SGI, which eventually went bankrupt. SPARC is still around, running gear made by Oracle, which acquired Sun. The big winner in the CPU market remained Intel and, therefore, CISC. In fact, the x86 architecture still rules, at least on PCs and servers, but not in mobile devices, where ARM (Advanced RISC Machine) now kicks butt. And for what it's worth, MIPS is now fighting ARM in the Android market, and Motorola's chip division is the long-since-spun-off ON Semiconductor.
So, five points here:
Vendors use stories as marketing strategies.
Vendor war coverage is always to some degree an exercise in misdirection (http://en.wikipedia.org/wiki/Misdirection_(magic)), even when journalistic intentions are worthy ones.
The real story is always much more complicated than vendor war coverage can characterize.
"Winners" never win forever, especially in tech.
"Losers" don't always die. Often they stay alive by selling out, or they thrive by finding niches and working them.
Now back to our four squid.
The graphic above The Economist story is a antique-style map (http://media.economist.com/sites/default/files/cf_images/images-magazine/2012/12/01/FB/20121201_FBD000.png) of the fantasy-fiction kind, drawn by David Parkins (http://www.davidparkins.com). It shows a large mountainous land, with the Sea of Content to the west and the Sea of Commerce to the east. Dividing the land are four throne-doms: Applechia, Google Earth, Amazonia and Fortress Facebook. A fifth, Empire of the Microserfs, is across the Sea of Content in the northwest corner of the map, bordered by the Cliffs of Surface. In Google Earth are Adsense-land, the Mirkwood of Regulation, the Wastes of Litigation ("Here be lawyers"), Pagerank Pinnacle (at the end of Algorithm Reach), beside which lies The Firth of Android. Appleacia has the iPhone Keep. Amazon has the Cloud Mountains and a volcano named Kindle. Between the latter and Netflix Nation (which lies above the Satrapy of Spotify) intrudes Pirate Bay. Offshore are the eBook Islands. On the opposite shore are OneClick Castle and Prime Port. Somewhere in the middle, between the Cloud Mountains and Fortress Facebook is the Lost City of MySpace. Out in the Sea of Content are small islands called RIM Rocks and Nokia. Atop the map is The Dark Offline. Floating in the Sea of Commerce is a Chinese junk flying the Samsung banner. A peninsula in the southeast corner features Secondhand City, the Bay of E and the Cape of Coin. There's a dragon smiling out of the Sea of Commerce, named The Next Big Thing. Finally, in the center of the map, between the four thronedoms, is an un-named body of water surrounding Identity Island.
Parkins' antique style also depicts antique substance in the making—because all four of the thrones (or squid, take your pick) are at least as affected by their own weaknesses as by the strengths of companies they are said to be fighting. And, because so many of us are at their mercy, their weaknesses are to some degree ours as well.
So let's look at those weaknesses, and then at where the rest of the action is, because neither are getting enough attention.
Doc Searls is Senior Editor of Linux Journal
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Why Python?
- Linux Systems Administrator
- Tech Tip: Really Simple HTTP Server with Python
- Build a Skype Server for Your Home Phone System
- Dynamic DNS
11 min 34 sec ago
- Reply to comment | Linux Journal
1 hour 10 min ago
- Reply to comment | Linux Journal
2 hours 20 sec ago
- Not free anymore
6 hours 2 min ago
9 hours 49 min ago
- Reply to comment | Linux Journal
9 hours 57 min ago
- Understanding the Linux Kernel
12 hours 12 min ago
14 hours 41 min ago
- Kernel Problem
1 day 44 min ago
- BASH script to log IPs on public web server
1 day 5 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
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?