Why Open Source Software/Free Software?
dwheeler writes: "I've just posted a major update of my paper,
``Why Open Source Software / Free Software (OSS/FS)? Look at the Numbers!''
Many sites give qualitative reasons for using OSS/FS, but this paper
emphasizes quantitative measures (such as experiments and market studies) on why using OSS/FS products is, in a number of circumstances, a reasonable or even superior approach. The paper covers market share, reliability, performance, scaleability, security, and total cost of ownership." Bookmark this for the next time your boss asks.
--
You miss something obvious when you talk about "Open Source" being bad for single shot, client specific applications.
These already ARE Open Source, most clients pay a service charge to have these application developed and they control the right to use the resulting application (most of those who have any ounce of clue anyway, I'm sure some are stung). In effect, the client is then free to take the work and extend it independently, redeploy it, place the code on the internet, anything. (This would be my experience from development contracts anyway - Perhaps some lucky people are getting away with harsher terms - I suppose Microsoft do).
Those choosing not to further distribute doesn't make it less like Open Source software to them - they can still have someone else work on it later and are not tied to a specific vendor (assuming the documentation is up to scratch). Many just don't realise the benefit of doing open distribution (it tends to save money to have vital, reusable parts of your system available for others to use and improve.
Sorry to feed trolls and all but I thought someone needs to respond.
When someone says the phrase "business model" people often think of various silly ideas that I would put more into the catagory of "scam". No, when I talk about business models I am talking about how you pay for software, not how to "make money" from software.
There was once a time when software was developed by companies in-house. It was secret, proprietory and built custom for that business. There was little forward progress in software methods as everything had to be reimplemented. Eventually, companies caught onto the idea that they could purchase generic tools from "software companies" which were often as good if not better than in-house development. Many companies sprang up to fill this need and the overall quality of software improved.
Open source offers a way to return to in-house development. Companies can have all the advantages of in-house development along with the free testing, debugging and features provided by contributing to community software. Co-operation can replace competition.
To address your concerns (or those who truely have these concerns, as you are obviously just trolling) I can personally state that it would be a relief if my job was not directly tied to the sale of a product. To put it frankly: customers piss me off. In-house development and maintenance is a much lighter atmosphere, without the headaches of release schedules or the lunacy of checkbox marketing requirements.
How we know is more important than what we know.
Lets not be zealots like are closed minded friends. Open source is superior for lots of applications, but not necessarily all applications.
A very specific program for a very small client (only) isn't a good open source project. Open source is wonderful if it works with/for a large communitee. Allow me to explain a little better. Its not a good open source project if it only works/only needed for one company and will never be needed again, because it won't reap the benefits of open source (no one will check the code for errors, or want to expand the code or add new features, etc...).
I am for open/free source, but I just don't want everyone to have a narrow view of open source. This probably isn't the best example (I'm sure that several people that reply to this will point it out). I'm just trying to explain that closed source still has its advantages, however few there may be.
--
"That's one small step for man..." "STOP POKING ME!!!!"
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
But I also feel that open source has some serious issues that need to be addressed.
1. It seems that quite a bit of open-source software works "just well enough", that is, the nerds can understand and figure it out, but the usability is not there for a technophobe. An example would be the Apache webserver, which a leader in it's class, even when compared to commercial software. However, it's not easy to setup - configuration is through text files, etc.
2. Documentation and Help: It's pretty well known that programmers like to code, not write documentation or a help system. Thus, many open source programs are poorly / not at all documented and have no online help if the user gets stuck.
3. It's hard for open source to compete against pirated commercial software. If everyone had to pay $200 for Windows and $500 for Office, Linux, StarOffice, etc. is an easy choice. However when Windows and Office can be obtained for nothing (and is, by most people), it's harder for open source to compete. If Windows is 'free' and Linux is 'free', most end users will choose Windows.
4. Ease of use and user interface. Open source programmers are not icon designers, color theorists, photographers, or graphic designers, for the most part, and it shows. Open source needs to figure out how to pay people in those fields to improve the GUIs of open source operating systems and applications.
Well, that was kind of long. Hopefully there will be (more) progress in these areas. I know about Mandrake - what is needed is Mandrake times 100.
My biggest problem with your article was use of words like "easier" and "faster." I saw no definitive words, no direct statements. Just statements of superiority over previous MS products. And some hints of superiority over non-MS products.
... sounds like bug fixes to me. I know guys who write patches the Linux kernel and send them in, and I have a funny feeling that the Linux kernel gets publicly released "modifications to the OS core to prevent crashes" a lot more often than any brand of Windows.
... hmm. A few things available for Linux that (more than?) equal the playing field: pgp, gpg, ssl-telnet, ssh, scp, IP tunneling over ssl, ssh, ssh over ssl, Netscape 128-bit encryption (and I'm sure there are more that I don't know about)
Having exactly 10 reasons gave cause for suspicion. And having only a few examples of corporations involved gave the suggestion that your data pool was awfully small.
"Modifications to the OS core to prevent crashes"
"comprehensive security"
IntelliMirror? Sounds like home directories over NFS, if you ask me.
And it really does sound as if you copied it off MS's website...
What's this Submit thingy do?
Reliability used an oversimplistic methodology, probing only for crashes and freezes based on random character input. This is not a metric that has anything to do with the average time between software failures and the seriousness of those failures in real-world software usage; it's yet another uptime-based quality claim. No commercial vendor would ship software that had been QA'd only through this ridiculously simplistic process, which would miss virtually all bugs.
Performance discussion dealt only with the speed of the base OS platform, not of applications.
The first numbers were based on abstract benchmarks rather than on comparison of real-world software packages. Instead, let's compare building a project with GCC vs. CodeWarrior, or browsing the web with Mozilla on Linux vs. Explorer on Windows or Mac.
When claiming a win on database performance, the article fails to note that the winner, while running on Linux, was DB2, a proprietary product from IBM, not an open source or free software database. Let's try MySQL under load against a commercial package instead.
The third performance test cited was for custom-built software, not applications which are used in the field. Again, it's quite possible the base kernel is faster, but in real-world conditions application performance usually predominates.
The web server benchmarks appear to be for static pages. Apache is known to be slower than IIS for dynamic content.
Security I'll grant is much better on Linux than any flavor of Windows, though a desktop Mac OS (not X) system is more secure than either.
The total cost of ownership issues associated with inferior user interfaces and typically inferior application software performance were not addressed. For instance, compare a shop of graphic designers using GIMP on Linux with one using Photoshop on Mac or Windows, and you'll arrive at a very different TCO conclusion. Ditto for a software engineering team using GCC vs. one using Codewarrior.
In short, it seemed to me a very partisan piece that ignored most of the issues associated with real-world desktop usage.
Tim
Historically, proprietary vendors eventually lose to vendors selling products available from multiple sources, even when their proprietary technology is (at the moment) better. Sony's Betamax format lost to VHS in the videotape market, and IBM's microchannel architecture lost to ISA in the PC architecture market, because customers prefer the reduced risk (and eventually reduced costs) of non-proprietary products.
IMHO, price is the reason that Open Source is kicking ass. Betamax, Microchannel, the Amiga, and a hundred others lost to inferior competitors that were simply less expensive but good enough. Consumers are almost universally concerned with getting the best "bang for the buck", and nothing delivers that better than Free Software(tm).
That's why Microsoft is so paranoid about Linux and the GPL. There's absolutely no way that they can compete with a superior product that's free (as in beer). People only buy Microsoft stuff because it's perceived as having value. As Windows licenses get more and more expensive, that value proposition gets shakier and something like Linux that's free (as in beer) looks a heck of a lot more attractive. The fact that Linux is faster, more reliable, and more scalable is just sweetener that helps seal the deal.
Thanks to Mr. Wheeler for this beautiful progress report. It's news like this that keep us Open Source advocates going.
This
Sorry, I am too busy at the moment to verify his references. Some of these don't look credible anyway.
(Two weeks later he makes an order for some MS products based off an advertisement from MS, without thinking twice).
Sure, open source works in practice, but will it work in theory?
Looking over the "paper" I noted some interesting things on just a quick viewing: 1)under "Performance Date" item 2 "GNU/Linux was the May 2001 performance leader in the TPC-H decision support (database) benchmark (``100Gb'' category)" .edu domain were used..." and if you look at the report there are NO .com domains represented. Well, gee. I wonder why there are so many linux boxes in the report?
Just pointing out that statistics represent those that present them.
Um yes, they did, but they did it on a machine that costs $948966.00. System description It was one of the most expensive machines in the running. The number 2 machine is an Win2k / SQL Server 2000 machine for a third the price. The Top Ten price / performance list is dominated by Windows 2000 / SQL Server 2000. TPC.org
2)The count of web servers in operation is a bit misleading as the source of the information states that "...host addresses of the
There are very few real things in this world...this isn't one of them.