Slashdot Mirror
Opposing Open Source?
Carl Nasal asks: "For a college class I'm taking, I have to write a research paper. I chose a topic of how open source software affects businesses, focusing on the use of Linux. While doing searches, I have actually found it hard to find opposing views of open source software. Mainly, what I'm looking for, are opinions, articles, looks, and evidence about the drawbacks of using open source software in business. They can either be online or offline, but preferably from reliable sources. (In other words, I'd rather not just have someone's homepage that loves Microsoft and hates Linux.)" The more constructive criticism we get about the drawbacks of Open Source, the better we can address and fix them.
You should talk to Jim Allchin, he has some non-biased views on open source and he's an industry leader.
http://news.cnet.com/news/0-1003-200-4833927.html
Kidding aside, it's probably relevant to your assignment.
This hurts open source software - closed source software generally costs money, which allows them to pay people like usability specialists, graphic designers, and technical writers (people who don't work for free out of goodwill). Currently it seems like only programmers are willing to donate their time to the open source software effort, and I see this as a weakness. Having a larger variety of developers would improve the quality of open source software.
I mean, how can anybody argue with the notion that a Cathedral is somehow inferior to a Bazaar? We all know Bazaars where it's at, that's what people look at these days, and travel to Paris and Rome and places to see and marvel at. Hardly anybody stops by the Notre Damme.
It's also pretty clear that anarchy by design and design by anarchy work well. After all, open source has brought some exceptionally innovative technologies to IT consumers in the past few years. We now can finally parse flat text files with greater speeds and more flexibility than ever before! And we keep bug-compatibility to programs written for 1960s computers that can be outperformed by a wristwatch! Now, that's what I call technology! Object orientation? component programming? that's for wussies who can't code in C, sh, or perl!
Finally, how can traditional software businesses compete with the multi-level marketing scheme of proselytizing users that become testers and developers and finally evangelists? It's obvious that all great engineering and scientific endeavours have been benefitted by active recruitement and by popular opinion, not some arrogant dude's idea of what 'right' is.
After all, software is tantamount to *speech*, not machinery. It should be spoken and transmitted freely, not designed and crafted like some piece of steel.
Oh, yeah, there was something else, but I am sure the replies to this will fill you in... something about advocacy or something...
Now, the ADVANTAGE to having the source is that you can technically work around any of these issues, but generally only by hiring specialists, at a great expense to your company. It's the big white elephant that no one's talking about in the middle of the open source bazarre: "Software freedom! You have the source! You are empowered!" Yes, but at what COST? For most companies, fixing an open source program to make it do what they want, just isn't a viable option. Plus, many in the community would view it as a "corporate co-opting of volunteer work," and the company could be flamed out of contention before they even decide on a policy regarding releasing improvements to the community.
Open Source does seriously empower expert individuals who wish to customize and improve software for their own use, and the community with which those individuals share the improvements. But that's not really a business situation.
I guess you've read Eric S. Raymond's The Cathedral and the Bazaar. You might be interested in also reading A Second Look at the Cathedral and the Bazaar. It's not directly open source criticism, and doesn't focus on business usage of free software, but it's a good read nonetheless.
Sig (appended to the end of comments I post, 54 chars)
Some examples:
And that's just a few of the more recent posts to his log. Don't get me wrong, Dave is a very thoughtful, articulate guy who's no Microsoft parrot -- he and his company, UserLand Software, were one of the authors of the SOAP specification that is proving so critical for future interoperability. He's just got a keen intelligence and is fond of applying it, which means he'll often come up with a different angle on things than you might expect. Go search his site and I bet you'll find, if not the answer you seek, at least some interesting questions.
-- Jason Lefkowitz
Read my blog.
In general, though, open source software is inferior to its closed source counterparts in:
Very little application or toolbox-level open source code is ready for prime time, in fact, whether we're looking at GCC, Mozilla, GNOME, KDE, OpenOffice, GIMP, or what have you. It's still hacker-oriented, better-enjoy-strolling-through-the-minefield stuff, and measurably inferior to proprietary solutions in most of the ways listed above.
One "killer argument" for many people here recently came in the form of consumer advocate Jamie Love's reasons for shifting his site away from an all-open-source footing.
Tim
another thing to consider is that there are no deadlines or date accountability in open source software. There's no "i have to get Emacs21 out by the end of july". It's done when its done. If its not done when you need it, then you just have to wait, there's not anyone you can call and complain. (course some people would say the same about commercial software: Diakatana, anyone?) The negative side of this is that if you're waiting for features, you could be waiting a while, unlike microsoft: when they say they're gonna have windows XP out by a certain date, they may push it back a coupla months, but if they say october 12th, its going on sale october 12th. If they said it was going to have a CD burning program, email client, voice recognition software, image-editing software, and a new media player, they may be bad, but damnit they're there. In open source, you get a lot of "well we meant to include it, but... it didn't make the code freeze, sorry, mabey next version.
Another downside, as mentioned, is tech support. You can call microsoft and get tech support, but a lot of OSS companies are doing that now, also - when i bought Mandrake 7.2 from best buy, i got a card in the box that said that i had 30 days of help for free, from the date of install, and that was in the $30 version.
Of course, i have no right to complain, as i don't actually program, beyond "hello world"
~z
sig?
My god, this whole article is like some kind of special troll trap! Maybe Slashdot is going to delete the accounts of anyone modded up on the thread... (are you listening, Taco?)
What do I do with all this crap? Do I start posting reasoned replies? That would be troll-feeding, and might take hours. Do I mod them all to hell? Not really fair, since they asked for anti-OSS, but they're all so, so... WRONG!
It's like having my eyelids forced open to watch the XP launch or something!
Aaaaaugghh!
Quick, click on the Science section! Ah, that's better...
"You can't get something for nothing." - my grandfather, on the stock market and Reaganomics.
Open Source is not a problem, unless you are running a business off it. You want to run the business off supported commercial (not necessarily proprietary) software. This means, you PAY for it. Paying may mean spending the $30 on a RH 7.2 boxed set or $1000 on Windows 2k Server. The thing is you can moan all you want but the difference between the licensing costs for AIX or Solaris is much higher than the licensing costs for Windows 2000. This difference is far higher than the difference between Win 2k and Linux. That is why proprietary UNIX is losing market share (picked up by Linux and Windows 2k). Although BSD is also losing market share, it is doing so more slowly than Solaris, et. al. and I think that it will recover (BSD losses appear to be due to fewer new machines being bought, Solaris, AIX, etc. seem to be due in part to active conversion in certain market sectors BSD is FAR more stable than Linux, though, and will probably retain at least niche markets).
My point is that your business software has to be supportable as well as inexpensive. If you can get support from a vendor, then OSS is great. Otherwise it is dangerous at best. And what if your vendor goes out of business-- you may be better off than if it was completely proprietary, but it may be more likely to happen if you choose a product form a company like Eazel than if you choose a Microsoft product. Can you survive? Yes. Assuming you can support the software yourself. IMO, this is the main reason for BSD's loss of market share to Linux recently is the difficulty in finding people qualified to support it and/or good vendor support (though anyone who knows Linux well should be able to transition to BSD will minimal study-- just most people don't know that-- though the boxed set of BSD has an Awesome manual).
Business questions:
1: Is it reliable enough?
2: Is it vendor supported?
3: Will my vendor go out of business and leave me without support?
LedgerSMB: Open source Accounting/ERP
Solaris 2.5 had a routing issue (I don't remember all the details from back then, but it was a bit complex). I spent about 2 hours diagnosing it w/o even needing to shut the system down and had it identified, and had a solution. But the boss didn't like the solution, so I was instructed to call SUN to get support. After 2 weeks of calling, being called, messages left, being forwarded around, the answer finally came back "Sorry, we don't support that, but our consulting people can build a customer solution for you". So I asked them to make a proposal and send it to me so I can give something to the boss in writing since it would cost money. Their estimate was $20K to $30K of consulting time and we wouldn't get either exclusivity or source for the results. My boss laughed at that. And while he still felt SUN should have just "fixed it", and that I should keep calling until they do (I thought this to be a waste of time), I finally did convince him to let me try out my solution. So I put a small Linux box running a 50 MHz 486 on the LAN with one 10 meg ethernet card, and default routed all the Sparc 2000 traffic through it. Performance actually improved. The boss not being entirely happy with a Linux box handling mission critical traffic, ended up opting to buy a well decked out Cisco 4700 to do the job (which it did just fine). Of course if it ever failed (it didn't) we'd have been down for a few hours before a replacement would arrive. If the Linux box were to die, we had replacements ready to go (I had Linux loaded on about 80 old no longer used hard drives sitting in storage, and we had plenty of old PCs around).
now we need to go OSS in diesel cars