Slashdot Mirror
No Competition Between Open and Closed Source?
techie writes "MadPenguin.org is highlighting the lack of competition between open and closed source applications. The author writes, 'Is there really the level of competition in the open source world that we see in the closed source world? This is something that has been stuck in my mind lately as I have been told so many times by closed source developers that by opening the code you are creating your own competition. Today, I'm here to explore this theory and hopefully prove why it's false.'"
What a great article. Maybe one day someone will write a relevant one about how and why GNOME and KDE compete, for example, and why. I'll be looking forward to that one.
Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
" Mozilla was reported making roughly $70MM for 2006" I'm curious how in the heck did it make that much? More power to them if this is true, but I thought the only way to make money in the FOSS arena was via support lines. As for competition I dont think it's the same as in the closed source world. In FOSS, there might be friendly competition, but that just drives a better product.
Have you ever chosen between using Apache and IIS?
Have you ever chosen between using MySQL and DB2?
Have you ever chosen between using OpenOffice and MS Office?
Have you ever chosen between using PHP and Active Server Pages?
(IANAL)
I haven't seen an EULA yet, closed or open source, that didn't waive any and all responsibility or fitness for any purpose.
Then again I've never reviewed any of those for life-critical applications.
More Twoson than Cupertino
Find free books.
What? Beryl is by far the finest window manager available, and window management is separate from widget sets on all major operating systems (you can use custom widgets all day in Windows if you want) so I have no idea what you're talking about. Certainly Ubuntu with Beryl has been no less reliable than Windows or OSX (I have both here available to me, in fact surrounding my Ubuntu system...)
Beyond that, it's not true at all. Blender is neato but there are several commercial packages that do more. CAD/CAM is another area owned by proprietary software. (I'm not even aware of a Free/free feature-based 3d modeling package.) Whatever else you say about Microsoft and Sun, M$ Office kicks the crap out of Open/StarOffice in more ways than it falls behind. There are other examples, but I'm bored.
Remember Unix? Yes, I use it today, in the form of Linux.
Linux is not UNIX but it is Unix. And if you don't know the difference between the two then you're not qualified to complain about me splitting hairs; if you DO know the difference between the two, then you will surely agree with my statement. Unix is to UNIX as Open Source is to the Open Group. Or something.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Better to know the bias than have no clue what their bias is. Everyone is biased, might as well know up front what theirs is.
Do the new versions of IE have tabs?
Yes they do, they must care about the competition then.
Umm, no it isn't. The article talks about the difference between the amount of competition among closed source applications versus the amount of competition among open source applications. It doesn't really mention competition between open and closed source applications.
With that cleared up, I had a hard time understanding exactly what the article was supposed to be saying. It seemed like a "Rah! Rah! Linux is Cool!" piece, but without any really well defined thesis. There were statements like "Appealing to the 'Home-sumer.' Hate them or love them, Linspire has proven that OEM can be a sustainable business model for their Linspire OS, based on the Debian code base " in a section entitled "Forget Windows and OS X: Just Try Linux." The weird part of this being, it doesn't mention anything about why a person should try Linux instead of Windows or OS X, just that it is profitable for the company selling it. I'd almost think it was intended as a comment for the OEM crowd, but OEMs have no option to purchase OS X, so that doesn't make sense.
I'd say that was my major problem with this article. It didn't make sense. Sure it made a statement or two that made sense and included some facts, but as a whole it just didn't add up to anything. What was the author trying to prove and to whom?
Does opening your product up risk a competing fork? Yes.
Should you, who wrote the software, be best placed to support and develop the product? Yes.
So does the competing fork stand much of a chance? Only if you drop the ball.
Think MySQL. We could fork it, but why bother?
Of course, sometimes forks do succeed - like Xorg. Which turns out better for the community. And that only happens when there is trouble with the original that can't be rectified.
P.S. Please don't link Matt Hartley articles, he has not been insightful in any article I have ever read. Feel free to look back through his previous nonsense.
Legal responsibility? You mean that big blurb in every EULA about a page long which says in so many words that they will never, ever take any responsibility for anything this product may or may not do? Show me someone that's gotten a dime out of a bug in any off-the-shelf software that fucked their business. They're there so the PHB can blame them, but they'll never pay damages. At best you get some free help so you won't make a stink and/or keep drinking the kool-aid, that is all.
Live today, because you never know what tomorrow brings
Closed Source is all about competition. If you want to make a new image editor in a closed source model then you are going to end up competing with Photoshop at some point or another. You can compete based on price, features, etc... And lets face it at $600 a copy for Photoshop it isnt that hard to compete in terms of price.
Open Source is admittedly more about co-operation and some degree of competition. This is why you have projects like Gimp which seem to overshadow other OSS image editing software. If you want a feature and you already use a software you are more likely to submit the idea to the project or if they are knowledgeable in coding do it themselves and offer it.
After all Open Source is all about not having to reinvent the wheel everytime you want to build a car.
09F911029D74E35BD84156C5635688C0
+2 Troll is Slashdot's way of saying groupthink is confused
Not really. I'm currently in the pre-alpha stage of a project to create a racing car simulation. There are two great projects in this area right now, torcs and rars. I've used both and I like them both, I have nothing against them. But I just thought that, first, I would like more emphasis on the physics simulation part that neither of those projects emphasize much, and, second, by starting my own project I would have a much better control on several other parts that I'd like to give more priority, such as network play, for instance.
Maybe nothing will come out of my project, after all I'm doing it in my spare time, but if I do eventually publish it, there will exist a third FOSS car racing simulation out there. OK, it will be more like a sixtieth or so, but most of the other projects are stopped at a rather preliminary stage. Take a quick browse through sourceforge and you'll see that there is no lack of competing pieces of software in the FOSS arena.
Sure, take a look at Linux. You can buy support for an embedded Linux project from the same company that will sell you support for several closed source embedded OS's. There are plenty of projects with commercial backers who will sell you support and service contracts including taking on legal liabilities.
Just because we as informed users are able to make use of equivalent FUNCTIONALITY it does not mean that it is an equivalent good in terms of the commercial world.No two of anything will ever be equivalent in every way. OSS tends to have restrictions attached to redistribution of the code, while it also provides a guarantee of competition in future bidding and an emergency exit strategy.
Note that I'm not saying open source is bad, or that closed source is better, merely that the two tend to be completely different when you look at all sides.Actually, open source code is simply a feature of software. There is nothing inherent in OSS that gives it any negatives compared to closed source software, although a given offering from a given company or organization may well have negatives compared to other open and closed source offerings. They are inherently different, but only in that OSS has a feature that closed source offerings do not.
Ummmm, Apache vs. IIS? Is this a trick question or something?
Service and support: the best and worst I've gotten were on commercial products; the free software I've used has tended to have good support, and you can buy service and support for free software. With proprietary software, either you can get support from the vendor, or you can't get support. Moreover, an organization selling support for free software needs to do a good job to stay in business, unlike normal commercial customer support, which is usually considered a cost center by the software vendor.
Legal responsibility: to the best of my knowledge, all software is equal here, in that nobody will accept legal responsibility. If you think any commercial vendor accepts responsibility, you've never read an EULA. The most I've seen one of those accept responsibility for is that there is, in fact, enclosed media, and the floppy or CD-ROM or whatever will remain such for sixty or ninety days.
Software has its own characteristics, and there are good reasons not to accept legal responsibility when distributing it. They apply both to free software and proprietary software.
Unfortunately, I don't know of any software where the creating company is liable for its effects. This means that this is a false comparison. One could just as well claim that unicorns are more suitable than horses for commercial purposes.
I don't know about every piece of software in the Universe, so if somebody could point me to a piece of software that is sold normally (as opposed to requiring a written and signed contract for distribution) that accepts responsibility for any problems, I'd be very interested.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
The same way that 90% of the articles make it to Slashdot: by making broad, controversial claims sure to spark click-through and reader responses which in turn garner more click-through and ad revenue. Most people don't read the articles anyway, so each new article posted is just a chance for people to regurgitate the same old arguments they've already had thousands of times with the same people winning with the same ideas.
Tell me again how OSS teams aren't reinventing the wheel?
(Also, I like how "supported" file systems seems to mean anything that may read some data from some type of files off of the target FS. Let's forget about writing, or supporting some of the esoteric oddities that have been developed.)
Talking about the Church of Emacs, Richard Stallman was asked whether it was a sin to use vi.
No, it's a penance
Sure, take a look here. The first Linux kernel was released in October 1991. If you had any reservations about its shortcomings, you can still get fixes for those today.
Let's compare that to a closed source equivalent. In 1991 I bought a copy of Microsoft Windows 3.0 for $40. It had several bugs and I used their support service to complain. Their answer? Those bugs would be fixed in version 3.1. So I asked, when would they send me my version 3.1? Their answer: I could buy version 3.1 as soon as it came out. No, I said, I didn't want to buy version 3.1, I wanted the bugs in version 3.0, for which I had paid $40, fixed. I wasn't interested in paying $45 more to get the additional features in Windows 3.1, all I wanted was the Windows 3.0 for which I had paid $40 working correctly. Can't be done, was their answer.
Now, let's see again, how exactly do you define "service, support, AND legal responsibility"???
And you know what's the worse of it? Although they have, 16 years ago, disclaimed all responsibility for the bugs in Windows 3.0, its copyright won't expire for several decades... Oh, yeah, *LEGAL* responsibility, indeed!
Check out Quiken's tax software EULA (if the software makes a mistake Quiken pays the IRS fines for making the mistake. One year they laid out some serious cash over a bug.)
As someone that has paid very little for software in the last five years, I would seriously consider buying quicken for linux the EULA would make it worth a look, to me at least.
Work bio at MMWD