Casual_blog/content/tech/WhatIs_OpenSource_and_FreeSoftware.md
2024-06-03 00:50:17 +03:00

8.1 KiB

+++ title = 'WhatIs OpenSource and Free Software' date = 2024-06-02 +++

Defenitions

OpenSource Software (OSS) - Software which source code is open to read/edit/distribute, and to use for any purpose.

Free Software - Software which respects basic user freedoms (by GNU)

User Freedoms

  1. Freedom to use program to any purpose
  2. Freedom to inspect and modify program for your purposes
  3. Freedom to distribute copies
  4. Freedom to distribute modifications

Sounds familiar, right?
But, Opensource != Free Software.
We will talk about it later

Movements

Open Source Initiative (OSI) - Movement that supports OSS.

Free Software Foundation (FSF) - Movement that Free Software.

Licenses

License protects developer from liability.

OSS uses Permissive licenses. Permissive license just allows user to use software for any purpose and states that source code is open to read/edit/distribute. E.g.:

  • MIT license
  • BSD 4-Clause
  • Apache 2.0 License

Free Software uses Copyleft licenses. Copyleft license complies 4 basic user freedoms. And it's is more restrictive.
For instance - with permissive license company can privatize source code by making modifications and claiming it's their code, so they free to hide source code. But in case of copyleft license - company should make source code available and with same license (so any further modifications will be Free Software). E.g.:

  • GNU GPLv3
  • GNU AGPLv3
  • GNU LGPLv3

So, proprietary tools may be based on OSS with permissive license, but not with Copyleft license.

Difference

So what's difference between OpenSource and Free Software?

It's idealogy of proggramers.

The priority of OpenSource developers is to make a reliable and efficient tool that, to some extent, can replace commercial analogs.

And the priority of “Free” programmers is to provide the user with the mentioned freedoms in the process of creating a reliable and efficient tool.

It's still not clear exactly what the difference is, but I'll explain now.

Example

For instance, Google's calculator for Android. It uses the permissive (Apache 2.0) license. However, the calculator on your phone is not free software. You can't install modified version of this calculator on your phone, OS won't let you to install software with wrong signature, what disrespects user freedom #1:
1. Freedom to inspect and modify program for your purposes

Google knows about it and states it in FAQ, explaining this decision as they want vendors to be able do what they want (lock down users with unknown proprietary software).

pros/cons for developer

How OSS affects life of developer?

Cons:

  • Misunderstandings - as with any collaborative development, it's about communicating with people, you have to be prepared for differences in perceptions and approaches

Pros:

  • Motivation - By making program for your problem and giving it out - you help many other people to deal with their problems. {{< spoiler Example >}} Richard Stallman, developed a set of GNU utilities for everyone to use. His team put together what we see GNU/Linux to be today. {{< /spoiler >}}
  • Reputation - You become more recognizable in the community, you can be invited to events and offered jobs. {{< spoiler Example >}} H.D. Moore, the creator of Metasploit, got invited to a lot of events and became a Principal Investigator at Rapid7 thanks to his tool. {{< /spoiler >}}
  • Portfolio - If you're applying for a job, it's a plus if you have OpenSource projects.
  • Growth - By doing an OpenSource project, it will get changes from other programmers that will help you grow as an expert and raise your code skills. {{< spoiler Example >}} Going back to Moore, he got a big jump on writing exploits while working on Metasploit. {{< /spoiler >}}
  • Code quality - you will write code of high quality if you know that absolutely anyone can see it than if you write it on your own. {{< spoiler Explanation >}} In psychology it's called the Hawthorne Effect. {{< /spoiler >}}

pros/cons for user

How OSS affects life of user?

Cons:

  • Support - there may not be any, and project development may be over in a month. {{< spoiler Example >}} I so one youtuber who posted his script threw in a few improvements, but he abandoned the project. {{< /spoiler >}}
  • Security - there is no guarantee that the program is safe, downloading OpenSource utilities is no different from downloading cracked programs, unless you read the source code. {{< spoiler Example >}} A recent notorious example is the XZ bibliotheca, which almost put a backdoor on all upgraded systems. {{< /spoiler >}}
  • Liability - If the program misbehaves and causes data loss, no one will be held responsible but the user themselves
  • Documentation - Availability, relevance and accuracy of documentation is also not guaranteed. {{< spoiler Example >}} I remember I found one very specific Python library that solved my problem, but there was almost none documentation so I learned how to use it by studying its source code. {{< /spoiler >}}

Pros:

  • Price - take it and download it. All OpenSource programs are free to use.
  • Platforms - OSS often supports more platforms than proprietary software. {{< spoiler Example >}} Adobe intentionally does not develop a Linux version of Photoshop, although they have a version for MacOS. And conditional Krita, there are on all platforms, and even on Android. {{< /spoiler >}}
  • Ownership - what you downloaded will work on any other similar system, this program belongs to you (within the license) and you can not take it away. {{< spoiler Example >}} A musician had a prog like FL Studio that he bought 10 years ago. After that, several new versions came out that were very different from this one. Sevris online activation was disabled and his computer crashed. And because of that he couldn't activate the old version of the program, and tech support refused to help him, despite the fact that the product license allowed him to continue using the old version. And he needed this very version for his work. In the end, what he bought was taken away from him. {{< /spoiler >}}
  • Security - The user can make sure that the program is secure and meets the developers' claims or your needs {{< spoiler Example >}} remembering the example about XZ - the researcher found a backdoor, but in proprietary software, for example Windows, it would have remained undetected for some time.{{< /spoiler >}}
  • Customization - User can customize the program to fit his needs.
    {{< spoiler Example >}} Don't like the color of the window? Adjust it and use the program. Or you don't like some annoying pop-up or default settings. You can change it all. {{< /spoiler >}}
  • Community - any user can help a developer with a project. And it's not just about writing code, it's also about helping with discussing and suggesting new features, writing documentation, user support, creating bug reports, testing new version. Everyone can help in development, regardless of their skills.
    {{< spoiler Example >}} For example, the developers of Proxmox VE get more feedback from users than from companies. And some users themselves send them how to fix their program, and it's not just a quick fix, but a piece of code that fixes the problem thoroughly. {{< /spoiler >}}

{{< source >}} My Research for Conference (some of the related links): https://choosealicense.com/ https://stackoverflow.com/questions/3902754/mit-vs-gpl-license https://www.gnu.org/philosophy/open-source-misses-the-point.html https://dev.to/opensauced/open-source-101-a-beginners-guide-to-getting-started-37fb https://www.gnu.org/proprietary/proprietary.html https://www.gnu.org/philosophy/open-source-misses-the-point.html https://www.gnu.org/philosophy/free-sw.html https://www.quora.com/What-are-examples-of-open-source-software-that-are-not-free-software https://opensource.guide/starting-a-project/ {{< /source >}}