[SOLVED] The Difference Between Open Source and Proprietary Software (undergrad research)
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The Difference Between Open Source and Proprietary Software (undergrad research)
I am a student conducting research into Open Source software for my undergraduate dissertation. I am looking for the opinions of some linux users as to why they prefer using open source software and what they perceive as the main differences between it and proprietary software. In particular, I am curious as to what meaning, if indeed any, users and contributors ascribe to the open source community and how they view it on a less technical level. Hopefully you'll find the topic as interesting as I do. Thanking you in advance for your participation.
Open Source is software, whether free or not, that offers the program and its source code with a license that allows you to change that code and recompile it for yourself.
And obviously there are different levels/versions of that license.
Last edited by szboardstretcher; 04-19-2011 at 08:09 AM.
That's very interesting MTK358, could you describe further what you mean by proprietary software being "like a physical product"? I think I understand you but I'd like to know more.
Also, thank you stretcher for the very succinct technical definition, and that is a good point about the different levels of licensing, I should read about them, any suggestions?
Thanks guys.
Last edited by osanthropologist; 04-19-2011 at 11:01 AM.
That's very interesting MTK358, could you describe further what you mean by proprietary software being "like a physical product"? I think I understand you but I'd like to know more.
I didn't mean to say it's like a physical product.
I said that if software was a physical product, proprietary software would be a device that's designed specifically to be impossible for you to open, for no real reason other than to keep you from repairing it yourself or learning how it works.
1. Governments like open source because they can see what they're using and if it's secure. A good example is Microsoft word: how many people realise that the doc format may preserve deleted text, which can be recovered, with potentially unpleasant consequences in some cases?
2. Open-source projects get their bugs removed more easily: as they say, with enough people looking at it, any problem becomes simple.
3. Many Windows users get free-ware that is closed source; if the author looses interest or drops dead, the program dies. Actually, abandonment can occur even with commercial software, as was the case with Adobe's FontStudio.
Ok, I see what you mean. You said, that that "feels wrong". How do you mean?
I'm sorry if it seems like I'm asking stupid questions, I really appreciate your helping out.
At least in my experience, open source software allows your data to remain your data and won't use crap like changing file formats to force you to upgrade. Or worse, abandon your data completely.
It wasn't all that long ago that I wrote my thesis on Word for DOS (the last decent version of Microsoft Word in my opinion). I've still got the files, but Word no longer reads them.
You also might look into the mess the pharmaceutical industry is in over proprietary software. Since the FDA can request background data for up to 20 years after a drug approval, companies have to store it. Frequently that means that copies of both the hardware used to generate the data and the software used to analyze it (and hardware to run the software) have to be kept for 20 years as well.
As the owner of a small business, I've REALLY appreciated a couple of things about FOSS as well. First is the complete and total lack of issues around licenses. Companies that rely on proprietary software usually have to spend a non-trivial amount of time/money/people to make sure they are in compliance with their licenses. Do some looking into the Business Software Alliance to see the horror stories that can come out of not being in compliance. The second thing I like about FOSS is the ability to very quickly and inexpensively test out new software. That way we pay only for what we know we are going to use and we will know that it will meet our needs.
Free and Open Source Software (FOSS) can be available commercially or as non-commercial software. The “free” in open source software refers to the Free Software Foundation's (www.fsf.org ) definition of 'What is Free Software'. The freedoms at the core of free software are defined as:
The freedom to run the software for any purpose;
The freedom to study how the software works and adapt it to your needs;
The freedom to redistribute copies so you can help others; and
The freedom to improve the software and release your improvements to the public, so that everyone benefits.
@OP you can find loads of information at the above links.
So Hangdog, you've found F/OSS to be mainly a commercial asset? Do you think that it fits well into the current format for software distribution that exists? Why do you think proprietary software is so huge none the less?
MTK, why do you think that is, that people aren't being allowed to understand these things? Is it purely commercial, or does it have more to do with people's general ignorance about technology?
David, as I understand it what you're saying is that F/OSS is more transparent and promotes innovation, would you agree with that? If so, can you tell me how you think that is the case?
MTK, why do you think that is, that people aren't being allowed to understand these things?
Becasue the license on proprietary software says so. That's basically the definition of proprietary software: you aren't allowed to understand it or see the code, because it's inner workings are a trade secret.
On the other hand, open source tends to look at software not as a product that acts like a magical "black box" that does a certain action, but as a mathematical algorithm that anyone should be able to examine and adapt for their own use.
The more people involved in something, the longer it will take to agree on anything
More hands = More mistakes
FOSS, GPL or Gnu, the maintainer will have the decision as to apply changes. Just like any project you have a maintainer(project leader), lead members along with major contributors. Unlike propriety where the programmer(s) must produce viable code on a daily basis. Error or bug fixes are harder with propriety. Adaptation is even harder for propriety software than open source.
You have to look at the way things do fork in the FOSS/GPL/Gnu because of different viewpoints or ideas. Why do you think there are so many Gnu/Linux in the world now? Better wheel? Look at the variations of software apps between distributions. Sure there are core apps but some organizations do require or need special apps or adaptations.
A big issue for any project is the manner in which errors, adaptation or even simple subs are submitted for content or program utilities. 'git' is one way, wiki is another limited way for communication between members. Any project does require documentation at some point in time. So why not have enhanced project notes available via a board that could be centralized.
Most serious programmers, either closed or open have unique tool boxes that sometimes are not shared unless justified compensation is agreed upon in some way. Snippets may appear but not all crunchers will give up the whole box. FOSS doesn't mean that I have to give personal code source unless I utilize the core along with my code. I can make changes without revealing my portions but I must release the original content. In house my snippets can remain mine.
My perspective as an end user is that open source software is more likely to a) be free as in beer, and b) be available on the multiple platforms that I run (I run both Linux and Windows every day).
If we're limiting the discussion to open source software on Linux, then open source software is more likely to work, and work optimally. The reason is the following. Closed source software on Linux either has a short shelf if it's dynamically linked (because library changes are more likely to break it), or suboptimal if it's statically linked (because the linked-in libraries become outdated compared to what's on the system).
Several posts in this thread have touched on how open source projects are managed. For that topic, I recommend this free book:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.