4 ms·
'“open source” is, except in pathological cases, also “free”' There is a substantial category that this leaves out, that I wouldn't call "pathological": commer
by leephillips 10y ago
'“open source” is, except in pathological cases, also “free”'
There is a substantial category that this leaves out, that I wouldn't call "pathological": commercial or otherwise proprietary software where the source is provided as part of the deal. The license may allow you to recompile for different machines, modify the code for your own purposes, but not redistribute.
EDIT: I may be wrong in the sense that the "access to source" I'm talking about may not be in the "open source" category, depending on how that is defined.
- s3krit 10y ago> I may be wrong in the sense that the "access to source" I'm talking about may not be in the "open source" category, depending on how that is defined. You're correct in that you're wrong :) The Open Source Definition [1] states: >The program must include source code, and must allow distribution in source code as well as compiled form. So having access to source/'source available' would not qualify as open-source or free software. Incidentally, when Amazon announced their new game engine 'Lumberyard', which is 'source available', there were places online claiming it was open source. Of course, that wasn't the case because it's not licensed under a free or open-source license and you are restricted from sharing your modified versions. [1] https://opensource.org/osd-annotated https://opensource.org/osd-annotated
- piaste 10y agoI never quite got why GNU decided to consider the freedom to access the source code and the freedom to modify it as a single bullet point. To me, they're fundamentally distinct concepts, and furthermore the former is VASTLY more important than the latter. Without the ability to check a program's source code, and personally compile it from that source, I am putting my hardware totally in the hands of the developer. I must trust that his program will do what it claims to do, and if it doesn't I can do absolutely nothing about it - other than threatening to take my business elsewhere or sue, which are merely the generic last resorts available for every kind of abuse or fraud. And even those will not shield me as long the program's misbehaviour goes undiscovered or unproven. It's pretty straightforward why this is a very dangerous situation when handling data of any importance. However, if I can view and compile the source code, but not modify it, then I wouldn't say the loss of freedom is remotely comparable. If I see that the program contains objectionable code, then it is unfortunate and perhaps frustrating that my only option is to reject the program in toto, but I cannot see how I can legimately consider myself wronged. I was offered a product with all the information required to make an informed decision, the product simply wasn't good enough. A food analogy: closed source is like having to buy food without the ability to examine its ingredients. Open-but-non-free source is like having access to the original recipe but not being allowed to take out the parts you are allergic to. It's a shame, but your health isn't in any danger.
- leephillips 10y agoI'm almost entirely in agreement with you, although I would say that the important distinction is between being able to access/modify the source code on one hand, and to redistribute it on the other. The right to access source and modify it, but not distribute, puts code in a similar category as books; certainly there is no restriction against making marginal notes or corrections in my own copy of a copywritten book, but putting the original or modified versions online for free download, or selling copies, would be illegal.
- piaste 10y agoGNU seems to agree with you, since they categorised the right to redistribute on its own as freedoms 2 (original) and 3 (modified). Of course, they also "consider [all non-free software] equally unethical", so from their point of view listing the four freedoms separately or as a whole should be pure cosmetics.
- nsgi 10y agoTrue, but it's less relevant now with web and phone apps that are sandboxed.
- piaste 10y agoThat's true, but I would argue it's counterbalanced by modern apps being (for the most part) always online. While we have more control over what data they can access, there are far worse things they can do with the data we do choose to share. In the pre-internet days, I could write my sensitive documents in a closed-source word processor and pretty much the worst thing it could do was silently corrupt or alter my file. Now, a sufficiently malicious word processor could very easily upload a copy to its developer's servers, and make such activity nearly impossible to detect as long as it had a legitimate purpose to phone home.
- retro64 10y agobut provide telemetry data back to the coder.
- 10y ago
- dragonwriter 10y ago> There is a substantial category that this leaves out, that I wouldn't call "pathological": commercial or otherwise proprietary software where the source is provided as part of the deal. This is not "open source" software by the open source definition. Free Software advocates claiming that this demonstrates that "open source" software is not free software is like open source advocates claiming that the existence of free (of charge) software -- "free software" in a manner of speaking, though not by the definition set by the FSF -- being available without the source being released under a license which meets the open software definition means that "Free software is not open source". The FSF definition of free software and the OSI definition of open source software are practically identical in real-world application, as is demonstrated by the fact that essentially all real-world licenses on which both the FSF and OSI have taken a stand as to compliance with each entity's definition of the class of software they are concerned with fare the same under both definition.