EOF - Markets in Three Dimensions
Old analog televisions had controls called horizontal and vertical. One kept the picture from falling over sideways, while the other kept the picture from sliding off the top or the bottom of the screen.
I think we need similar controls in our heads when we look at the product categories we call markets.
In the world of free software and open source, we mostly care about the horizontal: creating code, standards and other means for expanding markets sideways, toward the horizons. We work to keep both developers and users free from capture in the vertical markets we call silos, so they can do more stuff in more ways. We don't often ask “Where would we be without silos?” because we know. We would be free to build and use anything we want, out in the market's wide-open spaces.
Still, innovation happens in silos too. Many of the technical graces we take for granted would not have happened outside the walls of silos built by Apple, Canon, IBM, Intel, Sony and other large companies with ample and hardened intellectual property portfolios. Linux itself was developed originally (and still primarily) for Intel's x86 CPUs. Much of what we take for granted in chips from Intel and other makers is thick with intellectual property protections we would hate to see applied to our own software work. Every large maker of original electronic products (including all the companies listed above) produces between dozens and thousands of new patents every year, adding to portfolios that muscle licensing income and deals of many other kinds. Occasionally, companies do battle in court, but most of the time the dealing is quiet. If revealed, it is only through pro forma small-print disclosures in documentation.
What matters is that these portfolios give large makers the confidence and security they feel is required to produce original and appealing goods for which there is little or no competition. This is an ideal to which Apple, for example, constantly aspires. Back in 1997, not long after Steve Jobs returned to lead Apple after a long interregnum, he killed off cloners of the company's computers. Here's what I wrote about it at the time in an e-mail to Dave Winer (which Dave later published):
To Steve, clones are the drag of the ordinary on the innovative. All that crap about cloners not sharing the cost of R&D is just rationalization. Steve puts enormous value on the engines of innovation. Killing off the cloners just eliminates a drag on his own R&D, as well as a way to reposition Apple as something closer to what he would have made the company if he had been in charge through the intervening years....
Now Steve is back, and gradually renovating his old company. He'll do it his way, and it will once again express his Art.
These things I can guarantee about whatever Apple makes from this point forward:
It will be original.
It will be innovative.
It will be exclusive.
It will be expensive.
Its aesthetics will be impeccable.
The influence of developers, even influential developers like you, will be minimal. The influence of customers and users will be held in even higher contempt.
The iPod, iPhone and iPad each not only fulfilled all six of those requirements, but also redefined their market categories in the vertical dimension. That is, they grew the range of things that could be done with a given device, and the size of its marketplace. The iPhone in particular redefined the smartphone market and enlarged it far beyond the narrow range of possibilities allowed by combinations of mobile phone makers and mobile phone companies. New kinds of applications by the thousands burst out of the ground like a geyser. But all are contained inside Apple's silo, where they move only through the company's sphinctered approval and sales processes.
In fact, far more can be done on Linux (notably Android) and Symbian OSes than on iPhone's, just given the open nature of the former and the closed nature of the latter. But, thanks to Apple, there is much more to imagine doing outside that company's closed and private silo.
This is the point at which some suggest that open-source goods are derivative, rather than original. But that's not the case. We still happen to live in a time when investment in closed, and original stuff is greater than investment in the open and original kind. As long as that's still the case, we'll have the Apples of the world aiming for the heights while the rest of us build out the widths and the depths that characterize wide-open marketplaces.
Doc Searls is Senior Editor of Linux Journal. He is also a fellow with the Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at UC Santa Barbara.
Doc Searls is Senior Editor of Linux Journal
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.
Sponsored by AMD
If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.
Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.
Sponsored by ActiveState
| 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 |
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Validate an E-Mail Address with PHP, the Right Way
- Technical Support Rep
- Senior Perl Developer
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Introduction to MapReduce with Hadoop on Linux
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
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?




2 hours 3 min ago
4 hours 57 min ago
5 hours 22 min ago
7 hours 51 min ago
8 hours 24 min ago
8 hours 25 min ago
8 hours 26 min ago
8 hours 28 min ago
8 hours 29 min ago
8 hours 31 min ago