The Care and Feeding of Open Source Software 174
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."
The real reson (Score:5, Insightful)
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.
Re:The real reson (Score:3, Informative)
So tiny that Balmer spents a considerable amount of time each year flying out to meet governments and institutions in an effort to persuade them not to migrate to Linux.
Microsoft crushed (almost) all competitors in their main markets, OSes,
Microsoft has failed to control or dominate the server market, and is experiencing strong competition from Linux.
productivity suits
I don't see Open Office being crushed.
and browsers.
Erm
Re:The real reson (Score:2)
OpenOffice only exists in its current state because of the good graces of Sun and StarOffice. Where would it be had Sun not built (read paid for) StarOffice first, then broke off OpenOffice?
Re:The real reson (Score:2)
Re:The real reson (Score:2)
So? How is this relevant? It's still a strong competitor in the Office market.
You could just as well say 'Microsoft Office only exists in its current state because of the good graces of Microsoft'.
Re:The real reson (Score:2)
Yes it is. And I hope it makes huge gains. But my comment speaks directly to the main article, 'The care and feeding of Open Source'.
Where would OO.o be today without intial care and feeding from Sun?
Re:The real reson (Score:3, Insightful)
I see what you mean. However, I was replying to the post that said that Microsoft has 'crushed all competition'.
Where would OO.o be today without intial care and feeding from Sun?
Not very far. Which is why the 'Sun is as bad as Microsoft' attitude which is common on Slashdot is so wrong. Sun has provided one of the killer apps for desktop Linux.
Re:The real reson (Score:3, Insightful)
Yes, you are right. Part of what I meant by 'strong' is that Open Office is powerful enough to compete, even though it does not have a big market share yet.
http://www.users.on.net/~farnik/wikicgi/wiki.pl?M a rketingFLOSS
An interesting post, but I disagree with many points, based on personal experience. Not even MS Office is 100% compatible with
Re:The real reson (Score:2)
Re:The real reson (Score:3, Insightful)
You started your reply seemingly to show him he's wrong by limiting your response to discussion of the last year or two and showing off the recent successes of FOSS.
His point wasn't that there aren't good alternatives. His point was that if you look back further than a few years, MS did eliminate the competition in many realms. The alternatives you list now are a result of that.
-N
Re:The real reson (Score:2)
No. Microsoft has been trying to dominate the server market for years, and has never succeeded. The competitors in that market have changed (with Linux replacing Unixes and proprietary systems), but Microsoft has remained just another player.
Re:The real reson (Score:2)
In specific server markets MS dominates completely. They basically have the same enterprise market share (in a much larger market) that Novell once enjoyed, and even though they are losing slowly in this market they will remain a key player for at least two upgrade cycles. In the Internet server market MS has always been an also ran, and what share they have is doomed.
Re:The real reson (Score:2)
There is no such market (at least that I know of). Microsoft competes with Linux at the low end (where Microsoft has a significant presence), and Unix + Linux + other Oses at the high end (where Microsoft has few sales).
They basically have the same enterprise market share (in a much larger market) that Novell once enjoyed,
Actually, Novell is still enjoying a share of this market - it just has not grown as fast as Microsoft and others.
Re:The real reson (Score:2)
No, as you see below.
Microsoft's market share has increased only modestly, but their commercial competition has dropped precipitously.
No. For this to be true there would have to have been a phenomenal growth in FOSS in the server market, as the server market as a whole has grown, If MS has grown modesty, and all *commercial* competition has dropped 'precipitiously'.
This is not t
Re:The real reson (Score:2)
Re:The real reson (Score:2)
The parent (which is what I was replying to) was making assertions I felt needed correcting, for example that 'FOSS is a tiny nuisance in Seattle'.
Re:The real reson (Score:2)
I think IBM and RedHat may well disagree with you!
Re:The real reson (Score:2, Interesting)
it was greedy asshat's like Gates and company that turned free and open source into a dirty secret.
and the closed source thing was not common until the mid 80's I remember getting my very first IBM-PC and it came with the sourcecode to the bios in the back of the manual.
FOSS is simply taking back what was the norm for computing when it started. it's not bored people, it's people that know what is right and are doing w
Re:The real reson (Score:3, Insightful)
Furthermore, WordStar was never open, WordPerfect was never open, Magic Wand, Electric Pencil, CP/M...the world of software was not a free software garde
Re:The real reson (Score:3, Informative)
I did a number of projects on PDP 11s in the late 1970's and early 1980s and often had to buy software for it. In one instance I remember paying £3000 for a Pascal compiler. In another, I paid a similar amounts for both a Unix System V licence and for Emacs.
By the beginning of the 1980's independent database vendors such as Oracle were selling software (our company competed for a while with similar
You have the wrong meaning of open source (Score:2)
That 1970's software often included the source code. I certainly remember the basic interpreter on our school's first computer came with an entire printout of the source code (it was assembler). There was also the source code to the assembler. The first company I worked for sold CP/M software that came with the entire source code (the FinalWord word processor, also called Mince and Scribble). In all these cases the soft
Re:You have the wrong meaning of open source (Score:2)
But all (apart from possibly the unix packages - I can't remember) that I mention did NOT have source.
Re:You have the wrong meaning of open source (Score:2)
You did not say ".. and often software did not have source code with it". You said "...and often had to buy software for it".
Please explain why I should not conclude that you think open source / FOSS means free of cost to you.
Re:The real reson (Score:3, Interesting)
You paid money for Emacs?
Do you know if RMS got any of that?
Re:The real reson (Score:5, Interesting)
When RMS decided to start GNU, the first thing he did was a complete rewrite of Emacs based on the earlier versions. This was licensed under the predecessor of the GPL, the Emacs Public License (or something like that.)
Again, this is working from memory, so don't trust the details, but I think this might explain where Emacs fits into the Free Software scheme of things. Please, anyone, feel free to correct me!
but what about the programmers? (Score:3, Insightful)
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
Re:but what about the programmers? (Score:5, Insightful)
Gah! (Score:2)
(eagerly awaiting the day that somebody calls himself a "hobbeast").
Re:but what about the programmers? (Score:5, Interesting)
Let's take a current project. GIMP, for instance. A viable competitor/alternative to PaintshopPro (not Photoshop). Where could the GIMP today be if there could be a dedicated team of fulltime developers? i.e. people getting paid to create and update GIMP, and nothing more.
One of the reasons GIMP is gaining popularity is because it is free as in beer. Not because it is an especially 'good' or easy to use tool, but it costs nothing to use. (Don't get me wrong, GIMP is fantastic at what it does and how it was built). Most people don't actually care about the philosophy behind FOSS. GPL? Whazzat?
For a tool such as GIMP, selling hardware, support, and installation doesn't work. Those income generators work at the corporate level, not the personal level. So how could the GIMP team get paid for producing GIMP (or similar level tools/programs)? Is it possible to do?
How many FOSS tools could move off the '0.0.2 alpha' stage if there was a team of fulltime developers that could also actually eat while doing it?
Re:but what about the programmers? (Score:2)
wasn't there a film gimp, that some film studios have put money/time into directly to get features they want?
donate if you want, or use shareware or other payware if you'd think that they will give you the better software in 10 years time.
look at paintshop pro if you want to look what gimp could be with fulltime paid developers(note, i have no idea if gimp actually has some, in some firm, churning
Re:but what about the programmers? (Score:3, Informative)
Yes, but most people care even less about paying hundreds of bucks for buggy software that is vulnerable to viruses, with EULAs out the wazoo and built-in obsolescence.
The reason why proprietary software is so popular in people's homes (I'm not talking about corporations) is because 1) They don't really have a choice. They use what comes with the computer they bought or 2) they just copy it for free from some computer savvy
Re:but what about the programmers? (Score:2)
Re:but what about the programmers? (Score:2)
Re:but what about the programmers? (Score:2)
Re:but what about the programmers? (Score:3, Insightful)
I'm a webmaster, and my customers get their websites delivered with full source. (And no documentation! now if that isn't open-source...
The way I see it is that you can make money writing software, be it closed or open, as long as it's custom software. Commodity software is a different story - you c
Re:but what about the programmers? (Score:2)
Re:but what about the programmers? (Score:2)
I can make money off the software because it is custom software. If the customer wanted some commodity software (perhaps a CMS), then they could get it for free or for a price I wouldn't be willing to develop it for. If I wrote custom accounting systems instead of websites (which I will likely do this year), the same would be t
Re:but what about the programmers? (Score:2)
"The point is that those who get the software, also get the source code, and that they are allowed to do whatever they want with it"
This is exactly how any software company works. How often do you think the actual programmer keeps the rights to the software that they write when working for a company? Now, when your company gets the source code for the software, I seriously doubt that they are going to release that source code on the internet or by any means for that matter, effectively making that
Re:but what about the programmers? (Score:3, Interesting)
Ah, I see. What you missed is that I develop software for customers, not employers. This means I retain the copyright. In addition to that, I grant the customer full rights to the code as well.
The difference between that and working for them is that I can use the same software in another project. This reduces development time and bored
Re:but what about the programmers? (Score:2)
now... according to the article, if you have something very re-usable, you can keep your limited niche, or you can go oss and leverage the work of others for y
Re:but what about the programmers? (Score:2)
A lot of companies do this---most notably Linux distributors. IBM does it, Sun does it, and so do a whole raft of other companies.
The idea is that the gain they get from improvements is greater than the loss they potentially take due to making the code available to the competition. If it's a GPL type licence, there's also the added extra that if the competition use those improv
Re:but what about the programmers? (Score:5, Insightful)
I used to work in company that produced wireless routers (for our internal usage only; unfortunately we never reached the stage to sell them). They were based on Linux. In propriatery world, we would have to buy licence for OS. Then, we would be limited in changes we could made to them. And many many related things (no documentation, no source of drivers...). Company with 3 developers would have no chance to make anything similar.
So what is the point: Instead to write OS from the scratch; to write drivers and similar things we used existing free technology. My main task was to write bash scripts, to patch kernel and similar. Other guy wrote sofware for automated control.
Basically, we did not try to reinvent flowerpot hole (i.e. writing something that already exists), we focused on new value - i.e. things that were specific for own company.
I can say, without FOSS, what we tried to do would be totaly impossible. In this case, FOSS created 10 new jobs.
(Unfortunately, they lasted only one year, but it was not related to FOSS.)
In more general terms, FOSS enables you to move from general things to company specific things. All companies calculate taxes same way - but many many companies have their own in house built software for that. At the other side, there are no two same companies with exactly same business logic. FOSS, in theory at least, allows you to spare resources from coding tax logic (common tasks) and to transfer them to coding support for your business logic (specific taks).
To be honest, this happens also in propriatery world. SAP has same tools for all companies, but their (expensive) consultants will (hopefuly) customize their software for your own needs.
Re:but what about the programmers? (Score:2)
Who'd have thought that you could built something that works that way?
Re:but what about the programmers? (Score:2)
I am not sure that a company that never got a product to market is the best
Re:but what about the programmers? (Score:2)
Re:but what about the programmers? (Score:2, Insightful)
While it's true that a large amount of this is taken by such items as military, aerospace, and big enterprise systems, there is still a large body of sma
Re:but what about the programmers? (Score:2)
Actually they are briefly mentioned as "software that has no commercial viability" and then pretty much ignored for the rest of the article other than as the "FOSS corner case".
Re:but what about the programmers? (Score:2)
That has been my experience. It is the type of software that is largely invisible to OSS other than as frameworks and libraries (which are often incidentally useful to these types of applications).
Re:but what about the programmers? (Score:2)
From my own experience I've worked entirely on in-house projects, they were occasionally sold or given to external customers, but were never developed with anything other than internal use in mind.
Re:but what about the programmers? (Score:2)
I'm getting sick of this repetitive FUD by anonymous posters modded up. Probably marketing 'droids.
Forget philosophies. FOSS is simple statistics. With 6,000,000,000+ [census.gov] people in the world and widely used software it is a statistical certainty that somebody somewhere will have both the means and motivation to write good software. And when one person writes it millions of people can use it. Open source software and commoditisation is simply supply-and-demand and the market in action.
---
DRM - Democracy Re
Re:but what about the programmers? (Score:2)
-- so say confucius
It's Not? (Score:5, Funny)
It's not?!?
Damn!
Be honest (Score:5, Funny)
Theres no need to explain it as anything more then that to non-geeks.
Re:Be honest (Score:5, Funny)
Re:Be honest (Score:5, Funny)
Just sayin'.
Re: (Score:2)
microsoft and this article (Score:5, Interesting)
if we look at this historically, isn't Microsoft already dead?
certainly this article makes it clear that Linux may well enter a stage where it is an accepted standard, and has crushed the previous groups.
in a way, isn't that what Microsoft already did? they were once the upstart defeating the giants of IBM and Apple. history repeats itself.
I certainly don't think we'll see the death of MS for decades, if ever, but we may just see them seriously reduced
this article certainly provides a good explanation for that, in my opinion anyway - it seems pretty clear cut. perhaps someone can refute that?
i'd be interested to hear ideas...
Re:microsoft and this article (Score:2)
Every business and society is mortal (and already dead) from a historical perspective. It may be valid, but is generally not useful - and can even be a somewhat poisonous world view.
Re:microsoft and this article (Score:2)
Re:microsoft and this article (Score:2)
Re:microsoft and this article (Score:2)
Re:microsoft and this article (Score:2)
This is what I'm hoping to see. I don't want Microsoft dead, I want them deflated. I want them in a position where any closed source, patented extentions to accepted industry standards or trying to lock thier customers in to an Microsoft only world would be to thier detrement. I want Microsoft in a position where have to follow the rest of the industry, to only stand on the technical merits of
Paints a pretty picture (Score:5, Interesting)
Re:Paints a pretty picture (Score:2)
But I dont think FOSS goes further than step 4. Its already apparent from the server OS market. FOSS is never going to completely dominate.
The OS market -- server or otherwise -- is a bad example, because it's just too young. BSD has been around long enough to have had a good shot, but its legal status was clouded for some crucial years, and its license has deterred the sort of industry contribution that has accelerated Linux development in the last few years. Linux, on the other hand, is only 14 years
Re:Paints a pretty picture (Score:2)
it's just too young
BTW, just to be clear, I mean that the serious FOSS entries are too young relative to the speed of the market as a whole, not that the market itself is too young.
Re:Paints a pretty picture (Score:5, Insightful)
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.
Re:Paints a pretty picture (Score:2)
so if you got an innovative idea you have FREE TOOLS to make it happen.
Re:Paints a pretty picture (Score:2)
To me, it seems that people often get that impression because with most OSS, you can see the development.
They release 0.x versions to the public, you see the app evolved from a buggy and featureless start up to a release 1.0 version (ie. Firefox).
With commercial software, all the development phase is hidden and it seems to everybody that a finalized product just appeared from nowhere while in fact
Re:Paints a pretty picture (Score:2)
Too deterministic (Score:3, Insightful)
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.
Re:Too deterministic (Score:3, Funny)
... he is a Marxist?!?
Re:Too deterministic (Score:2)
My argument may not have been as clear as it should have been, but I believe there is a strong connection btw. the marxist approach (esp. with respects to communists trying to skip stages 2 - 5 [bourgois]).
Re:Too deterministic (Score:2)
I think you missed some other possibilities!
Re:Too deterministic (Score:2)
For example it mentions that operating systems have not been OSS for much of their lifecycle - this is not quite true.
Original Unix was developed in OSS fashion, as was numerous code for Z80-style microcomputers. I am sure I a missing a lot :)
Also Stage 1: invention is often started in academic community in precisely OSS fashion.
GPL is simply a legal tool to protect the right to create and is an outcome of an era when one must ask for a license before hum
Stage 5 Today (Score:4, Interesting)
Some current Stage 5 situation: (FOSS community begins to slowly but inexorably erode the technical lead held by the commercial offerings)
WS_FTP [ipswitch.com] --> Filezilla [sourceforge.net]
Winzip [winzip.com] --> 7-zip [7-zip.org]
I'd be interested in seeing what factors it takes to push the above into Stage 6 (FOSS version dominates).
Re:Stage 5 Today - you forgot (Score:2)
Moveable Type [moveabletype.com] --> WordPress [wordpress.org]
Although I think WordPress is almost or at Stage 6.
For more info see this blog: http://www.elise.com/web/a/an_overview_of_the_webl og_tools_market.php [elise.com]
In August, WordPress had 4% market share of the blogging software community, whereas Moveable Type had 7%. Yes, I realize that Blogger (at 30%) and LiveJournal (at 23%) are the reigning kings, but I'm speaking of software you can install and host yourself; both Blogger and LiveJournal are hosted servi
Re:Stage 5 Today - you forgot (Score:2)
Re:Stage 5 Today (Score:2)
Just thing of Wikipedia.
Stage 6, obvious superiority. (Score:2)
How about the integration of many superior and excellent parts that closed source software can never match? As an example following yours, I give you Konqueror which integrates local file management with the features of the above utilities and more. By using free archive software and free networking software all the functions above are folded into a si
The Author seems ignorant of Mac OS X (Score:3, Informative)
2) He keeps calling it Macintosh, which is the general name for the hardware. The operating system is called Mac OS X.
Other than that, an interesting enough article.
Re:The Author seems ignorant of Mac OS X (Score:2, Informative)
Craig A. James
Can OSS survive? (Score:3, Insightful)
"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?
Re:Can OSS survive? (Score:2)
It will survive. This is why the GPL is so important: people can't "sell out". The liscence keeps them honest and their software fully Free. It is because of this protection that OSS cannot be fully co-opted by a corporate system of control.
Not sure about this (Score:3, Insightful)
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.
Not just that (Score:2)
...but FOSS folks make some pretty dumb moves that hamper their own success. Open Office isn't popular because of the cost. It isn't popular becuase it has a steeper learning curve than the next version of MS Office to an existing MS office user (i.e., everyone).
Unfortunately, the OOo evangelists think their UI is superior, so they have no inclination to change...thus shooting themselves in the foot.
Conclusion mostly correct, reasoning wrong (Score:5, Insightful)
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.
Re:Conclusion mostly correct, reasoning wrong (Score:2, Insightful)
Sure it's free if the developer is a hobbyist, but remember hobbyist developers can just as easily develop closed software.
So your whole argument breaks down. Abandoned projects on SourceForge costs millions in lost time. My time is pretty valuable. If yours is not I have a job for you. You can do it in your free time!
The article basically states that in software markets where there is
Civil Rights (Score:3, Insightful)
No imagination necessary: that's exactly what we're talking about. Only the enemy has changed: domineering big business instead of a domineering government.
P2P doesn't fit his model. (Score:2)
Is there something wierd going on with P2P software? The MPAA/RIAA induced arms race perhaps?
Re:P2P doesn't fit his model. (Score:3, Informative)
2. expansion happens. ftp bots. scp. rsyns. napster.
3. consolidation. napster, ftp, scp die. other propriatary p2p apps keep going. gnutella pulls a lot of supprort, www keeps going. bittorrent is a new idea, but pulls in and gets some supprot which will soon be pulled together with more secure tech. gnunet gets started based on p2p with security in mind.
4. maturity in a few years. secure p2p. gnunet. oss and private companiest that use propriety protocol
Re:P2P doesn't fit his model. (Score:2, Insightful)
P2P is still very young (technically) but it's mature from a business, can-we-make-money-from-this perspective.
That's a laugh! (Score:3, Insightful)
"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.
His "Hard Core" reasoning flawed. (Score:3, Insightful)
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.
Re:His "Hard Core" reasoning flawed. (Score:2)
It's a cumuative thing. (Score:3, Interesting)
The real benefit of free software is being able to chose what you want. I can think of a few places that are likely to have real innovation but I'm loath to offer specifics because some obscure package someplace may very well offer it. It's not like people can't very easily make their own version of any free program and sell it. The development problem will be making it as good as the free program when your resources are
Re:It's a cumuative thing. (Score:2)
Ugh, you make me repeat myself. (Score:2)
And my point was that the investment boom of the 80s and 90s was an anomaly. The whole NDA fad created by Ma Bell, and perfected in EULAs by Microsoft was a fraud. All the cross licensing, copyright, trademark and patent work was parasitcal and gets in the way of
software lifecycle (Score:2, Insightful)
Re:Marx knew it... (Score:2)
Well, yes. But the future is uncertain....
Re:Marx knew it... (Score:2, Interesting)