The Care and Feeding of Open Source Software
An anonymous reader writes "You might find The Care and Feeding of FOSS (Free Open Source Software) interesting. This article debunks a lot of the myths and misunderstandings about the open-source software development process."
... FOSS has flourished in recent years is a tiny nuicance up in Seattle. Microsoft crushed (almost) all competitors in their main markets, OSes, productivity suits and browsers. The only way to avoid this fate was to produce free software, using the same tactic MS has employed.
Another explanation would be: A lot of highly trained, intelligent and creative people have rather dull jobs, maintaining or servicing existing technology. They want to "realize their potential", and they do open source.
they need care and feeding aswell
ideology behind open source is nice of course, but some of us have to make living by writing code
open source isn't always the solution for everything
The article is interesting, and its nice to see an interpretation I had never thought of before, but another poster was right when he mentioned the Marxist angle to this particular interpretation.
Open Source software is simply too new to establish a model for this to follow - there are many different models that could be followed, and it is simply too deterministic.
The Marxist connection jumped right out at me, from this one quotation in the article.
The hard-core FOSS advocates would like to go directly from Stage 1 (Innovation) to Stage 6 (The FOSS Era) and skip the whole commercial part. They argue that proprietary software ownership is undesirable at best, and immoral or unethical at the worst.
But ignores capitalism and human nature, and the economic forces that help fund and drive the creative process in Western society. In spite of fundamental differences between software and brick-and-mortar industries, software follows the same first four phases of the lifecycle.
Come now, this sounds exactly like Marxism.. It is interesting that there has never been a self declared communist state in the world - they were always going through the SOCIALIST stage of the model. The article is essentially saying that they should follow a gradual evolution of ideas, but that is inevitable.
Determinism is dangerous to use in this context - you can't just sit by and wait for Open Source. 'Lifecycle' my ass.
"There's no success like failure, and failure's no success at all."
- Bob Dylan
Don't you mean Winzip -> Windows XP? Because thats what I see.
Its main effect is to take out all the small/medium players and polarize the market into FOSS and the commercial giants which is unfortunate because the smaller commercial endeavours are where (as far as I can see) most of the innovation tends to come from
Maybe a more positive way to view this is that FOSS commoditizes markets that are way overpriced. This is especially true of:
* Compilers and software development tools.
* Operating Systems
* Productivity suites
* Web servers & Application servers
* e-Mail services
Now even the tiniest organizations can use FOSS to gain an advantage. I was able to start a regional online advertising network for less than $500 by using a commercial, open source ad manager that I've retooled to fit my needs.
FOSS also tends to lag behind the technology curve so by the time it starts to mature the market has moved on, creating new options for commercial software so FOSS will constantly be chasing a moving target.
I have got to disagree with this on many, many levels. A great many of the innovations you take for granted now were invented via FOSS (try basically, the internet as a platform, web browser, email, etc). FOSS has nothing to do with commercial or not. It's about the app coming with the source with rights to modify (oss) or source + right to mod + right to redistribute (free). There are plenty of commercial apps that are oss. There are also commercial apps that are Free as in speech. I think what you are comparing, is for example, OpenOffice vs. MS Office, which compares a commercial closed source with a semi-commercial FOSS one. Even so, OpenOffice has capabilities that MS office does not and MS Office has capabilies that Open Office does not. The technology curve is more of a 3d wave than a 2d curve - it's possible to lead in one area and follow in another.
Don't assume that because an application is FOSS that it is somehow inferior to a closed source product.
-- $G
"Both FOSS and commercial versions may coexist, but commercial forces usually dominate the innovative process at this point."
As Corporate America embraces the OSS culture it will take what was once an "IDEAL" and find ways of turning it into something that is good for the Corporation.
I think a great example is in the Music Industry. A genre of music will develop in some obscure place creating something living and evolving and vibrant. Then the big record companies will discover it and then it starts. They milk it for every cent available until that great sound becomes lost in the watered down mass of "product" that they churn out. Soon the creative subculture has been bought and sold and cloned so many times it losses everything that was good about it. Could this be starting to happen with OSS. Red Hat has become a corporate entity. Suse is on it's way. When the cash offers becomes so large that OSS developers start to sweat and their knees get weak....will the "IDEAL" be enough any more? Will the culture survive or will it sell out?
"We will remember not the words of our enemies, but the silence of our friends. " Dr. Martin Luther King, Jr.
1. The market leader once gaining dominance will just choose to gravy train their product, ala IE.
2. The flow of new features goes from the commercial version to the FOSS version. The commercial entity apparently isn't capable of absorbing new features from the FOSS version.
This is a crock. A commercial version can remain hyper competitive even in the face of the "FOSS onslaught". There are numerous tricks than be pulled. Obscure or constantly changing file formats (ie .doc), cross integration with other products such that the whole "web" must be replicated to be truly competitive. And let's face it, not all software is an OS. Or an Office suite or a web server. Especially complex client server products can have dozens or even hundreds of interoperating processes; this stuff is a nightmare to replicate. You may find these tactics unpopular or even unethical but that's just the way it works in the real world. Large successful companies can and do make it painful in the extreme to erode their market share. The author seems to ignore the economics of market dominance.
As someone who works in a company which does FOSS and commercial stuff too, I obviously have a (financial) interest to watch this debate. Firstly, I find the trend amongst OSS developers to just build free versions of commercial stuff is very problematic. Yes you can say we're making a better version, but truth is, that many users will go with free from a financial perspective, not coz the software is better. So e.g. Microsoft/Apple/Adobe spends years of market research and focus groups to develop new features - and other people just copy it. I reckon most (not all) modern day FOSS is simply parasite-ware. Eventually there will be no incentive for anyone to make much new. Let's face it, we all have to eat so great, we can all starve together and eat from Paypal donations. Secondly, what is this absurd assumption in OSS is it so moral to make money off of selling software services rather than sellling code? Is this simply because most people writing into /. make money by selling their IT services.... My point is - is this a logical point or are you just simply fighting your own corner (as I am).
Lastly, will OSS become less interesting to end users as we move to a more network-based computing world? i.e. do I care whether it's LAMP or Java or MSFT behind the online service I'm using? The way to protect your code is to create a whole managed service web infrastructure and service behind it....
I have more to say, but you're probably yawning if you got this far...
I have to agree (mostly) with the author's conclusions (or at least the ones I didn't ignore :-)). However, I disagree with the reasoning.
FOSS dominance in most fields is inevitable. I'm not talking market share, I'm talking stable features. In a prorietary world, features cost money. Bug fixes cost money. Even worse than that, they cost resources (one can have money to do something, but not enough people to pay to do it).
Currently, proprietary providers live with a difficult economic reality. They invest 10% of their expenses on R&D and require at least a 5% total profit. This means that you need a 10.5:1 return on R&D investment in order for a feature to be worthwhile. Since not all development works out, successful features need to be even more profitable.
When you first start, there is lots of low hanging fruit and even a 20:1 return on R&D investment (what most VCs demand) is quite reasonable. As the product matures, features get more difficult and more and more of your R&D gets used up by support (bug fixes etc). Not only that, but by Brook's law we know that adding R&D resources slows things down (due to communication overhead). This means that's there's a practical maximum of resources that can be added to the project. At some point, development slows down to a crawl.
FOSS, by nature of the fact that there isn't an expected return on R&D investment, runs into no such problem. In theory, there are infinite resources availble to the problem.
If a feature is desired enough by someone, it will be implemented. The return on investment (benefit vs cost) only has to be worth it for *one* person. The benefit does not even have to be returned as money.
Not only that, but FOSS operates in an evolutionary way. HUGE numbers of resources are expended on projects which yield no results (just check the abandoned projects on sourceforge). But it doesn't matter. Those people eventually migrate to the successful projects. If I develop A and then discover B is better, I can abandon A with no cost to myself. Eventually the more successful projects end up getting more and more resources.
FOSS generally doesn't need to worry about Brook's law, because wasted effort is irrelevant. FOSS projects can afford *not* to communicate thereby duplicating effort. The popular version will win out and everyone can migrate with no loss (generally speaking) to themselves.
That is why FOSS feature/stability dominance is inevitable (generally speaking). So why doesn't it always work that way? Well the first problem is recruitment. At the beginning, there may be many different competing projects. Until the consolidation period (in the author's paper), there may not be enough resources in any one project to compete with a proprietary provider's VC backed investment. This is not always the case. A good example where FOSS was *way* ahead of the curve is window managers. I think most people would concede that OSX temporarily tipped the balance, but not for long.... FOSS dominance is inevitable. Good ideas will be copied, bad ideas abandoned and new ideas will be forthcoming.
The other area where FOSS does not dominate is in projects where there isn't enough interest to do development. Word processors used to be a good example. Nobody wrote one because nobody used one. Now there's are a few groups of people with a bee in their bonnet about office suites. Given enough time, most areas will probably be dominated by FOSS. They may lag behind the curve, though, if developers don't see the reasoning early enough.
Finally (whew!), feature/stability dominance != market dominance. I personally don't agree that IIE *ever* had feature dominance over Apache. However, market share is market share. The thing about FOSS, though, is that it never goes away. You can try to kill it, but it will just resurface a year later. With proprietary software, all you have to do is cripple or buy the producer. With FOSS, you are faced with the prospect of a never ending propoganda program (making your product even *more* expensive).
The *only* way for proprietary companies to successfully compete against FOSS is to make FOSS illegal. We need to be vigilant.
Listening to the most dedicated FOSS advocates, one could easily imagine the speaker was talking of civil rights, war protests, or women's suffrage.
No imagination necessary: that's exactly what we're talking about. Only the enemy has changed: domineering big business instead of a domineering government.
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
"Besides being portable, Unix happened to be the best operating system invented to date. Its kernel, its unified file/IO system, its security model, and its "shell" were all major advances. Unix quickly pushed aside almost all other operating systems."
That's a laugh! UNIX certainly stole a bunch of good ideas from MULTICS, and did invent a few, but "the best operating system invented to date"? That's just ludicrous.
If AT&T had sat on it, UNIX would have gone nowhere. They key innovation of UNIX was not technical, quite the opposite. What made UNIX what it was (and is) was "open source". AT&T Labs made the UNIX source code available with few restrictions to universities and researchers, and this is what made UNIX great.
Anyone who has seen early UNIX versions will agree that it was, in all honesty, a fairly mediocre operating system. Then again, the very first Linux versions released were, again in all honesty, not much to write home about either.
Since then UNIX (and Linux) has improved immensely on the technical side, but even today, UNIX/Linux is reinventing features of operating systems of the 1970s and '80s.
It is interesting that the author uses the unethical behavior of commercial software producers to say that free software advocates are wrong. Patents, FUD and other tricks the author mentions do not make commercial software more innovative.
The second assertion above, that embedded software is not well served by free software is simply wrong. Embedded development has swung to free software in a big way, as commercial software there was expensive, buggy and had all the other problems of closed source. According to the Free Software Foundations' last newsletter, the majority of embedded developers now make use of free software, at least for development. They will soon make flexible tools that will dominate the embedded market. The same development model, which is more flexible for servers and desktops works for embedded projects too.
The whole argument that closed source software provides swifter innovation is shaky. Many of the so called features are involve product lock in and other dirty tricks that cost you more in the long run. IBM and others are showing that you can develop free software faster than closed source and make a profit. The era of software development he looked at, where indeed many closed source projects were "innovative", is over. As he pointed out, many people lost lots of money in the closed source game and will be reluctant to risk it again. In short, the rush he saw was unsustainable and should not be used to judge the future. Software development itself has reached a Maturity phase where the tools needed are well known and available. Free software now has a combination of development, distribution and user tools that can not be matched by any single closed source thing. To say that rapid development MUST be closed source ignores the awesome and unmatched feature advancement going on with KDE, Gnome and others. It's somewhat insulting to say free software developers simply copy commercial junk.
Friends don't help friends install M$ junk.
Quote : Capitalism will continue to be a part of the software lifecycle as long as software is useful to society. It's a negative point of view, what if Capitalism is no longer usefull ?
P2P is in the 5th step of his model. I.e. there's no more money to be made in P2P so closed source houses do not really care about it anymore.
P2P is still very young (technically) but it's mature from a business, can-we-make-money-from-this perspective.