Hacker News new | past | comments | ask | show | jobs | submit login

Does this mean that react could be considered "available source" instead of "open source?"



I think it's a great illustration of the difference between "open source" and "free software." In this case the source is still openly published, but under certain circumstances you're no longer free to redistribute.


Personally I think it's a great illustration that even software developers lack reading skills.

Open Source means this, no more, no less: https://opensource.org/osd-annotated


A license (such as Facebook's) that prevents me from redistributing a modified version could still qualify as "open source" so long as simple mirroring wasn't restricted.

> In practice, open source stands for criteria a little looser than those of free software. As far as we know, all existing released free software source code would qualify as open source. Nearly all open source software is free software, but there are exceptions. First, some open source licenses are too restrictive, so they do not qualify as free licenses. For example, “Open Watcom” is nonfree because its license does not allow making a modified version and using it privately. Fortunately, few programs use such licenses.

> Second, and more important in practice, many products containing computers check signatures on their executable programs to block users from installing different executables; only one privileged company can make executables that can run in the device or can access its full capabilities. We call these devices “tyrants”, and the practice is called “tivoization” after the product (Tivo) where we first saw it. Even if the executable is made from free source code, the users cannot run modified versions of it, so the executable is nonfree.

> The criteria for open source do not recognize this issue; they are concerned solely with the licensing of the source code. Thus, these unmodifiable executables, when made from source code such as Linux that is open source and free, are open source but not free. Many Android products contain nonfree tivoized executables of Linux.

http://www.gnu.org/philosophy/open-source-misses-the-point.h...

(Pasted the most relevant portion in case you lack reading skills.)


> even software developers lack reading skills

A little condescending, no? Do you read (or expect everyone to) the EULA in full when you install Windows, and understand the implications of _all_ clauses? Or for that matter, the Privacy and User Agreements of any website you visit, e.g. Spotify, Facebook, HN (this very website), Netflix, Hulu, Google, etc., or software you might install, e.g. WhatsApp, Signal, iTunes, macOS, all the licenses visible and distributed with Android? What about your banks, and the actions they sneak in that give them the most freedom to do with your money/data under the law?

The text written in these agreements is foremost written for other lawyers, not you. Many companies have made them easier to parse, slowly prioritizing the user's ability to understand them.

Most people have fine reading skills. What you are misconstruing is an ability to understand and derive implications of legal agreements.


I think it's more of an illustration that for better or worse, most software developers just want to hack, and are willfully ignorant of what they consider peripheral concerns.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: