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
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide