The Implications Of Software Commodity?
comforteagle writes "David Stutz has written elegant piece over at OSDir.com titled 'Some Implications of Software Commoditization'. It explores the concept of commodification in a historical context while also seeking to discover lessons that might be applied to contemporary open source business efforts. David gets extra points in my books for including sugar, Shakespeare, open source, MP3s, and the British Empire in one article."
like all property/physical world analogies to information, the differences trump the similarities in every attempt at relevance.
the fundamental issue being that you can't copy a pound of sugar from one box to another and still ahve the same amount of sugar in the first box.
lysergically yours
Everyone knows that Shakespeare (who was a sugar freak) would have released his work as Open Source in an MP3 format if the British Empire hadn't stopped him.
Use Ctrl-C instead of ESC in Vim!
the fundamental issue being that you can't copy a pound of sugar from one box to another and still ahve the same amount of sugar in the first box.
You can if you clone it.
From David Stutz's website (http://www.synthesist.net/writing/commodity_softw are.html)
simoniker really just wanted to one-up David Stutz by including sugar, Shakespeare, open source, MP3s, and the British Empire in one SENTENCE! Is there a special karma bonus for that?
(Hey! I just did it too! Can I have the karma bonus as well? Nevermind the karma. Just visit my website and support the Creative Commons.)
This article was originally posted on Stutz' website. Since OSDir seems to be slashdotted, you can read it here!
42
While there are many lessons to be learnt from history, the human race in general seems not to care, actually let me rephrase that .. .. the people with all the money and the governments supposedly representing the masses but actually more likely on the pay check of said rich people/companies do not care in the slightest. They would prefer to opress progressive science by stopping technological advancement by whatever means necessary, because it would put a dent in their profits!!
If at first you DON'T succeed, Skydiving is NOT for YOU!!
I often used the phrase "the commodification of software" to represent what I believe is the critical force behind the rise of open source software. Broadly used software is now defined primarily by its capacity for networked data exchange of standardized commodity datatypes such as a web page, an MP3 file, a UNIX executable, or a Word document, rather than its application model and user interface. This short note explores the concept of commodification in a historical context while also seeking to discover lessons that might be applied to contemporary open source business efforts.
Commodity
The word commodity is used today to represent fodder for industrial processes: things or substances that are found to be valuable as basic building blocks for many different purposes. Because of their very general value, they are typically used in large quantities and in many different ways. Commodities are always sourced by more than one producer, and consumers may substitute one producer's product for another's with impunity. Because commodities are fungible in this way, they are defined by uniform quality standards to which they must conform. These quality standards help to avoid adulteration, and also facilitate quick and easy valuation, which in turn fosters productivity gains.
Karl Marx considers commodities important enough to begin his book Capital with a discussion of them. The first chapter concludes with a discussion of what he terms "the fetishism of commodities," from which the following quote is taken:
A commodity appears, at first sight, a very trivial thing, and easily understood. Its analysis shows that it is, in reality, a very queer thing, abounding in metaphysical subtleties and theological niceties. So far as it is a value in use, there is nothing mysterious about it whether we consider it from the point of view that by its properties it is capable of satisfying human wants, or from the point that those properties are the product of human labor. It is as clear as noon-day, that man, by his industry, changes the forms of the materials furnished by nature, in such a way as to make them useful to him.
Marx asserts that commodity markets are more about power, politics, and even religion, than they are about their actual underlying resources. Commodities exist to facilitate exchange (and, since this is Marx, to subjugate the laborer). They are a way to build up an abstract world in the image of commerce, rather than reflect a more natural order for the world. Commodities are a reflection of the politics of human values: the contracts by which commodities are defined, and the standards that form the foundation for such contracts, are more important than the inherent quality of the commoditized thing. This is a very important lesson to learn, and one which the open source community should heed when marshaling its limited resources.
Commodity, the bias of the world
Shakespeare, of course, always has something to say.
Here is a soliloquy that concludes Act II of King John on the topic of Commodity. It is delivered in the play by the bastard son of Richard Coeur de Lyon, who has just convinced England and France, at war with each other, to suddenly strike an opportunistic political bargain and ally themselves against the city of Angiers:
Mad world! mad kings! mad composition!
John, to stop Arthur's title in the whole,
Hath willingly departed with a part,
And France, whose armour conscience buckled on,
Whom zeal and charity brought to the field
As God's own soldier, rounded in the ear
With that same purpose-changer, that sly devil,
That broker, that still breaks the pate of faith,
That daily break-vow, he that wins of all,
Of kings, of beggars, old men, young men, maids,
Who, having no external thing to lose
But the word 'maid,' cheats the poor maid of that,
That smooth-faced gentleman, tickling Commodity,
Commodity, the bias of the world,
The world, who of itself is peised well,
Made to run even upon even ground,
T
David gets extra points in my books for including sugar, Shakespeare, open source, MP3s, and the British Empire in one article.
..."
"To MP3 or not to MP3, that is the question:
Whether 'tis GNUer in the mind to suffer
The slings and arrows of outrageous coffee with no sugar
Okay, do I get points now?
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
You can't copy a folio of Shakespeare from one book to another.
Oh, wait.
Commodities have two key business properties. First, competition is based on price -- the efficient low-cost producer gets the business. Second, commodities are standardized so that the same commodity from two different sources can be interchangable.
With regard to price competition, OSS seems to have a big advantage. Free beats proprietary on price any day. The only interesting question is whether OSS software makers are more cost-efficient ($/line-of-code) at developing new software than are close-source vendors. Perhaps this will come down to a competition between developing -world OSS developers who work parttime for free for OSS versus developing-world developers who get paid a fraction of the labor rate, but work full-time for commerical software vendors.
With regard to standards, I fear that Microsoft has made itself the de facto standard inspite of all the open standards bodies. Even the web seems to be moving into the MS camp. Websites are developed to display well in Internet Explorer, streaming media is often only available in Media Player, everyone uses MS Office, and soon many might be forced to use MS trusted computing. I'm not sure how open standards can re-assert themselves to commodify the playing field in terms of non-MS-controlled "standards."
Software won't be a commodity as long as one player controls the standards because one player has monopoly marketshare and everyone neds to be compatiable with that standard.
Two wrongs don't make a right, but three lefts do.
...have nothing on the even greater implications of hardware commodity and its impact on web server scaling.
The fact that software is approaching $0 in cost doesn't mean there are less jobs for software people, it just means that a great deal of what was purely IT 'territory' is now going to be dual role, with software developers having to know a portion of the business as well.
The large employers with their vertical silos inside the organization will fight (and loose) this change, while smaller employers everywhere are already reaping the benefits. Stop billing yourself as a 'software' guy and go get some background in operations accounting, marketing, logistics, whatever, but the days of the separate priesthood are numbered - your choices are a.) on top of the wave b.) not very palatable fish food.
I'm a sniper and while the target rich environment of the pre bubble economy is gone there are plenty of profitable things left to 'shoot'.
I am very easy to get along with, but I don't have time to waste being nice to people who are being stupid. -Theo
> It means that sites will get slashdooted within the first 30 seconds of being posted.
As oppossed to within the second 30 seconds?
If I see the word "commodity" one more time today, I am going to puke.
Since the beginning of the humankind, empires always has tried to repress freedom movements... fortunatelly empires always fall... is just matter of time... :)
As others have already noted - and which was noted in "IT doesn't matter" - is that the issue with packaged software is that everybody can buy it for a reasonably small price. In so much, it by definition becomes a commodity. However, packaged software covers only a small portion of the market for software. In-house solutions and so forth could not be considered a commodity if they provide a sustainable competitive advantage for some particular company. Imagine a software toolkit which allowed a company to estimate, with 99% accuracy, the future movements of markets in which they compete. It would be laughable to consider such a piece of software a commodity.
So what's the point of all this. I think what Open Source has done is pressure the big software houses to become more innovative than ever before. It's not good enough to come up with a good idea (a la MS Office or MS Windows) and tack feature after useless feature onto it just to get people to upgrade. Companies then need only buy software upgradesto "keep up with the Jones." However, there isn't any competitive advantage in this, and the economics of IT has borne that statement out - nobody has ever really revolutionized their companies using IT. What the software houses need to do is envisage IT products in terms of months of useful life, and not years, or even decades. The key issue here will become: "how long can this piece of software give me a competitive advantage before everybody has it?" Exclusive contracts with software houses will become the norm, before software is released "to the masses." Software products will be canibalized within months by the same company that originally produced it. Sales cycles will decrease to days, rather than months or years as it stands now.
Finally, for-profit companies will need to mobilize to head off the threat of Open-Source. Intrinsic motivation is a hard battle to fight, and software companies will need to fundamentally change the way they approach HR issues and corporate reporting hierarchies if they want to compete with a legion of programmers who write code because they want to and they enjoy it. Monetary compensation schemes simply can't bring that level of devotion to a task.
Yes, the software industry as we know it, and the software it produces, will become a "commodity." Companies that understand how to avoid this will just blow away their competitors by bringing fundamentally brilliant software products to market. And you know what? The customer, as always, will win, over and over again.
Bravo to Open Source for forcing this upon the industry.
here, which OSDir likely copied from.
VIVA1023.com | Political Fashion.
- Commodities are things that can be exchanged for one another. They are able to be sourced by and consumed by multiple entities.
- UNIX programs are commodities in a way due to the standardization of the core POSIX APIs.
- Document formats, such as the Microsoft
.DOC format, are going to change to allow documents to be used more as commodities.
- This is both good and inevitable.
It really didn't say a whole lot else. I mean, it was an interesting introduction, but I found myself looking for a page 2 on which the point would be made. Hrmph.You're special forces then? That's great! I just love your olympics!
... you can't handle a slashdot'ing!
According to Netcraft:
The site osdir.com is running Apache/1.3.24 (Unix) PHP/4.1.2 mod_ssl/2.8.8 OpenSSL/0.9.6c on Linux.
Bah!
This article is interesting, but rather than the commodification of software, it's more the commodification of data that's really being discussed. His examples and ideas really concern data format standardization and that standards are what allow data to become commodities.
In that sense, I agree completely... demand for "market" in distributable music spurs the popularization of a standard and an infrastructure for distribution (e.g. peer-to-peer networks). And I definitely agree that software should be written to take advantage of economies provided by using standardized data.
Of course, it's kind of obvious that demand precedes standardization, since standardization takes effort and some kind of demand must exist (even if it's just a, "Hey, wouldn't it been keen if...") before people will get off their duffs to figure out, formalize, and make available a standard.
How long has Shakespeare been around? 400 years or so? How about sugar? Well over 1000 years, right? My dad was in the room when the "first" computer program (calculating PI to 1000 places on the ENIAC) was run, and he's still using computers today. Any commoditization of computer software in the last, say 10 years, is surely coming on too fast to be compared with "historical context" that spans tens or hundreds of generations of humans. I would say that MAYBE 50-100 years from now, people could look back at today and make a statement like that, assuming that OSS doesn't go away in 10-15-20-30-40 years. There is just too much change right now to say anything concrete about where software is "going" (although I concede it's interesting to think about).
stuff |
I am thinking that OSS is a commodity in the sense that computer hardware was a commodity in the pre-PC days of CP-M and the S-100 bus. Jerry Pournelle had this mantra "iron is expensive, silicon is cheap" that a person would "invest" in a boat anchor cabinet, a good power supply, and an S-100 backplane and then plug in boards with memory, processors, and peripherals and upgrade the silicon while keeping the boat anchor iron.
This putting a computer together from parts required someone who knew what they were doing, and Pournelle plugged the idea of "system integrators", dudes who would in essence sell you generic hardware, but in their markup they were selling you a service of knowing what hardware was compatible with what and where to get the drivers for everything.
For all the talk of Linux weenies and lusers, the average Linux distro really is not an end user product, but it seems that the Linux savy could pull together pieces parts of software and put together systems tailored to the requirements of specific customers. You know, open and free software, but the money is to be made in providing services, and the service is being the propeller head who knows what software is out there and what works with what, and what configuration tweaks will make a customer happy.
The PC kind of changed Pournelle's model. The silicon was cheap, but the iron (cabinet, motherboard, power supply) started coming from Free China and later from Not-Quite-As-Free China and it became cheap, and with the business model of Dell, it is pretty much cheaper just to replace the whole system than poke around with doing your own upgrades.
As far as the software, the software has kind of moved away from this mix and match model as well. Sure, a Windows install may be as hard as some Linux distro installs, but who even installs software -- you buy the computer with Windows, Office, and networking already installed from Dell. So I guess the system integration has become a mass market instead of a cottage industry.
I am thinking that for Linux to catch on, there has to be some patron, some "angel", some big player to do the system integration and sell ready-to-run systems to the mass market. Is it Wal-Mart and Lindows? Is it SUN and their "Java workstation?"
You keep saying that word, but I do not think it means what you think it means...
Yes, usually a commodity is something cheap that has lots of competition- but that isn't the point. A commodity is 'something that is used to make other stuff(tm)'.
The point is that the good sold is used as an input to make other goods.
That used to be a 'big deal' when people with invisible hands were groping[for 42]... Now, ehh...
Oh, and I say Windows is not a commodity because it's not a goodThat's because I saw his very first post and created this account instead of criticising him anonymously. Read all his posts. They all suck beyond belief. Trust me, we are not the same person.
I think it means that developing software is in the toilet. You make any money by being an installer, an admin or by selling tweaks--competing with people who are also doing to same with the software you developed.
The main effect is that software is cheaper.
And if software is cheaper, people will buy more and in greater varieties.
What's the problem here?
If I have to spend $200 on Windows XP and $450 on MS Office, that doesn't leave a whole lot to go around to other vendors.
But if Windows was $100 (as it should be) and office was $130 (as it should be), then MS would not be so rich, but there would be lots and lots of other software vendors making money.
While I agree with most of this posting, I would go further.
Software production, in my experience, is NOT a freely-interchangable commodity., because programmers are not of equal ability.
In other words, software quality is not so much a function of the process used to produce it, as it is a function of the insight of who produced it. I see "software engineering" (and approach it) more as art than as a production problem. For example, while some art is displayed in museums, to be viewed over and over again by all, other art is bought by private parties, and never seen again..
I believe we should study the economics of art to understand how software fits into the marketplace.
The fact is that many would like software to be a commodity. But when you treat programmers as plowhorses, you end up with lousy art. Just like the parent posting suggests, those companies that see the difference will produce gems that will outshine the rest.
You're on the right track here. A commodity is usually defined as physical substance, such as food, grains, and metals, frozen orange juice, etc. which is interchangeable with another product of the same type. Equating Folgers with ground coffee is pushing it, but technically you are correct. The restaurant or diner is selling a hot brown liquid.
Commodity also implies both mass supply and mass demand, although these are rarely in equilibrium.
Calling software a commodity implies that it is interchangable. As Linux and F/OSS has grown and developed, it has become increasingly possible to substitute Linux and F/OSS for proprietary software.
Another quality of commodities is that they are priced pretty strictly by the market. Except in unusual cases where someone corners the market (and thus has monopoly control), the normal pressures of supply and demand determine price over time. If prices are high, others will want to profit, and begin producing the commodity. If prices are low, some producers will leave the market, decreasing supply. (Of course there are many other factors, such as the weather, that lead to shortages and surpluses. Trade groups can also collude to keep prices artificially high, basically operating as a monopoly.)
Because F/OSS can be distributed freely (as in free beer), and electronic distribution is so cheap as to be nearly free, it's somewhat of a misnomer to call it a commodity. When it is "sold" it is usually bundled with something else that gives it value. Hardware gives it value, IT sevices (development, administration, and consulting) give it value. The reverse is also true. It gives hardware value, even though it itself is free.
"Normal" commodities can be bought and sold on various commodity exchanges. Futures can be bought and sold. Physical objects can be exchanged. Also, because commodities are physical, there is a finite amount, even when there are huge surpluses. There is potentially an infinite number of copies of Linux, so demand will not outpace supply. Again, the limiting factor seems to be the supply of hardware and of support services.
Hmmmmm. Anyway, in case you couldn't tell, I'm thinking about all this as I type, so I don't have any conclusions or insights. Just more questions, really. Really a great topic. Too bad I couldn't RTFA.
It's not offtopic, dumbass. It's orthogonal.
The whole idea of software being a commodity is absurd. Intellectual property can't be a commodity. By defenition, intellectual property has no physical form, which is why there are so many laws protecting IP owners from those who would copy it ad-infinitum. A commodity is a thing that is physical, and one unit of it is interchangeable with another. There's probably better ways of expressing this, but maybe that will be my doctoral thesis or something.
"Those who would control the production and distribution of commodities typically seek not so much to harness network externalities, but rather, economies of scope. This economic phenomenon leverages consumer demand not by creating network critical mass in order to reap profits from exponential network growth, but rather by reusing the underlying commodity in many different ways. The rather obvious implication of this observation is that resources that can be used in many different ways are likely to attract more investment, and to penetrate society more fully, than resources that are very special-purpose. This, of course, will impact the choice of standards; an item that is low-level, simple, and easily integrated with other items is more likely to be useful as a building block than a special-purpose, complex, and highly proprietary item."
Blah, blah, blah.
He probably likes to say "utilize" where he could say, "use."
And he probably hangs out with Doc Searls.
And they drink beer and tell each other how SMART they are.
When we in the open source / free community develop and adopt a simple "good enough" user interface standard the same will happen in graphic programs.
I suggest that "eye candy" interfaces push mass desktop users away from our OS of choice. Push them back to MS word, excel, etc. A very simple and uniform user experience is needed.
in addition, I suggest: a interface standard will lead to more programming work, since a wider array of programs would be understandable to "average joe" users.
Therefor, I suggest that every desktop have two modes, the "hyper vanilla", and the personalized. At the click of, say, alt F1, the mode would toggle.
this would dramaticly ease tech support assistance and tutorial creation.
cheers
The funny thing is, as I read the comments here, everyone speaks of software as if it's a physical thing. Sure, it has a physical reference, but there's nothing you can point to and say, that's software, like you can with sugar or wheat. You can't buy a "pound of software", strictly speaking.
What can be commoditized is time; specifically, the time spent to create software. It can be rationalized, measured, spent, etc., and there is already an existing metaphor for compensating one for these various actions: the hourly rate. Software production costs time and money (or no money, as we'll see).
Read the whole discussion before you blow up.
In a sense, Free Software takes the whole paradigm of time having value and does away with it entirely. With Free Software, one cannot expect to receive money for the time spent. One creates software and turns it loose on the whole world, or some small portion of it and receives recognition (or not) from the receiving audience. Strictly speaking, if you receive money for developing something, it cannot be considered Free Software - somebody paid something for it.
In a sense, it is a slap in the face to software companies and to those of us who work for money. Free Software says that the time and money spent hiring a programmer and designers (or me) to produce a given piece of software was wasted: what y'all spent millions over the course of six months to develop, we can do for free in eight months or a year.
On the other hand, there is an argument to be made in favor of the greater public good. Software is expensive, and specialized software is even more so, perhaps out of the reach of some developing businesses. Certain types of software are important enough that perhaps they should be free, but determining which is an impossible task. An operating system - that's pretty easy; an MP3 player - not so easy. How does an MP3 player benefit the overall public?
To my mindset, money helps smooth over one of the basic problems of humans: ego. If we lived in a world where everything was produced freely and given freely, that would be great. But how do you compensate for that jerk down the road who sits on his ass all day and just takes and takes rather than giving back to society in some form? The answer is you force him to pay for the materials he uses and consumes. That requires money. Sure, he could work it off, but we've already established that he's a lazy bastard and won't work.
Thus, I have to come down in favor of paying for software. I don't think it can be properly commoditized in the same sense that sugar can. In fact, I'm not even sure there's a proper word for that type of a thing. What I do know is that certain forms of Free Software are a kind of slap in the face - saying that the time I spent and the education I paid for are worthless.
These are only my views. Pillory away.
To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
IP is the result of this equation: Time+Effort=Value* . This equation has to hold true for IP to be a part of a barter sytem.
"That which affords convenience, advantage, or profit, especially in commerce, including everything movable that is bought and sold (except animals), -- goods, wares, merchandise, produce of land and manufactures, etc."
Note that IP isn't excluded from the above definition, but is a part of. For IP can confer an advantage, give convenience, and generate profit all in the context of commerce.
*Note that services fall under this equation e.g. Mow lawn, fix roof, brush teeth. As well as physical goods.
Danny.
I have written over 900 book reviews
software is made as a good.. by a company.. same as shoes, or socks.. time was put into the design, not including production costs.. this is a far greater percentage of cost for goods with software...
Saying you should be able to copy any software, is as obsurd as saying you should be able to copy currency... if it is legal to copy the goods you didn't create, how about copying money you at least earned?
Michael J. Ryan - tracker1.info
Calling a "UNIX executable" (whatever that is) a standardized commodity datatype is so completely confused I cannot continue reading.
By the way, the decreasing critical facility of slashdot moderators is a consequence of "karma entropy." These days its all shits and giggles.
The referenced article really doesn't seem to say anthing meaningfully true. Even AC posts can be insightful.
Coincidentally, I've just been reading the original Halloween Document so when I saw the author's name, it rang a bell. He was talking about "commoditization"(in the context of protocols) back then, too.
BTW, for anyone who's never read the original Halloween doc, it's well worth a read. There's some amusing stuff in there about things being "stolen" from Unix and put into Linux, and how SCO are likely to be wiped out by Linux before long (and this back in 1998!).
Registering accounts later than some other chrisb since 1997
Sugar may have been around for thousands of years (as a harvested resource, millions as a chemical) but its only been a commodity for a few hundred; when the availability of sugar cane, international trading, the slave trade, the fashionability of New World goods (coffee, tobacco, chocolate and cane sugar) the emergence of a large middle class who could afford to buy foods they didn't really need, the military and entrepreneurial adventures of the European Empires, all combined to make sugar a product that had both a high demand and a large number of producers willing to cater to that demand.
Some commodities last for centuries, some for years, but it's not about the product itself, nor about the technology behind creating it once that technology passes a certain treshold whereby it's feasible for new entrepreneurs to enter the market with relative ease. It's all about the demand and the ease with which that demand can be satisfied, which is just as relevant here.
Where the fast rate of change with software does enter the argument is as a counter to the argument that software cannot be a commodity, due to the ease of copying it - the ease of copying it is balanced by the desire for new versions. The question remains though as to whether that balance is weighed evenly enough on each side, and as to whether the individual nature of some software (as a piece of craftsmanship rather than most commodities where you can painlessly replace one example with another) prevents full commodification.
The article makes a strange omission in not talking about computer hardware as a commodity. The commodification of hardware that happened with the emergence of PC clones had a tremendous impact on many software companies, especially Microsoft with DOS and later Windows. The important thing in this case is that we have a combination of the commodificaiton on one product (once IBM no longer had a monopoly you could replace any piece of hardware with hardware from a rival company, hence price and rapid cheap transport became a bigger factor in the business models of these companies, and the PC was a commodity) with the lack of commodification of another (while there was some choice for many application domains, many people were forced, or at least thought they were forced, to go with MS DOS and later with MS Windows as the OS). In this case the commodification reduced the total cost of ownership of a Windows system, enabling Microsoft to charge more for less when it came to their part of the package.
There are factors that prevent software from becoming a commodity. First and foremost is the fact that software is a piece of craftsmanship, rather than a harvested good, which is protected, by copyright and sheer issues of convenience, from being completely copied as a rival commercial product before it becomes obsolete.
Another is that, while copyright prevents the distribution of direct rivals (i.e. exactly the same item) by other legitimate businesses, the ease of copying means that free copies will soon be available, either legitimately or illegitimately depending on the license. Commodification itself tends to lower prices, arguably to the point of being "elastic" (completely at the mercy of the forces of supply and demand) but it depends upon one being able to rely on some return for your investment. Free software cannot be a commodity.
Yet another is the direct interference to prevent the commodification of software. Given the article's beginning with Marx it's worth considering Marx's prediction that the cost of labour would be elastic. This was proven false (at least in the context of industrialised countries of the last century) and ironically was partly a self-defeating prophesy; workers - inspired by Marx himself, amongst others - formed trade unions and won various guarantees regarding conditions and pay and as such made the cost of labour inelastic. Similarly there are many people who want to prevent software being a commodity - either because the wish to maintain profitable monopolies, or because they wish to remove the commercial aspect of software use. Like the trade unions it's likely that neither group will be completely successful (especially since they are pulling in opposite directions), but like the trade unions it may well be enough to keep commodification from ever completely happening. For bad or good we don't have much protectionism from governments anymore, but we have a lot from vested interests.
There are cases where commodification does happen to a certain degree. Ironically one of these is the case of games. Too much of the market games are the most individual type of software there is, they will make a point of buying one and not another. However another important section of the market they really will do the equivalent of "buying half a pound of software" - the important market that are relatively uniformed but who buy the games as a gift. This had quite a strong effect on the games market in the 1980s especially with the emergence of budge software houses that would sell items at STG 1.99 or STG 2.99.
There are also cases where commodification doesn't happen where one might expect. The PC clone became a commodity but Apple have managed to improve their lot by de-commodification of the computer. You buy a PC clone because you want a computer, you buy an iMac because you want an iMac. This is a matter of marketing, but it has strong effects (similarly the PC itself has become less of a commodity now that the average buyer has opinions, not matter how well-info
Replace the word software with journal submissions or peer-reviewed articles for a similar, time-tested approach in academia.
Is it a rule, that there's an exception to every rule?
Software may be free some day. But I'm willing to bet that there will still be a critical need for people who know how to use software to get a job done.
Not every problem will be solved by the open source community because most problems that exist in the real world are not solved by basic applications. Basic applications support the solving of big problems. But Complex applications solve specific problems.
I also would be willing to bet that problems will always outnumber solutions.
42 - So long and thanks for all the fish.
Stutz say "the presence of multiple producers stokes the furnace of competition (although perhaps only after protectionist governments and corporations are shouted down by consumers and crafty businesspeople)" However, in part of the research world that I work in, involving 3D geo-realistic and geo-specific databases for real-time simulation and training, it is the "crafty businesspeople" who have resisted commodification, pushing their own proprietary standards, hoping to make THEIR standard THE de-facto standard, while the government (DoD) has mandated real standards (e.g. sedris.org and the HLA).
blah balh trying to get karma back from bitch mods blah blah
The "Insert Quote Here" line is almost as predictable as inserting an actual quote.