6 ms·
Open source is about the source being open plus certain benefits. Free and open source software, a la Richard Stallman, is a totally different thing with a phil
by nickpsecurity 11y ago
Open source is about the source being open plus certain benefits. Free and open source software, a la Richard Stallman, is a totally different thing with a philosophy akin to how a virus operates.
A glance at fair.io shows an interesting attempt to provide OSS under a proprietary model. Many businesses are fine with whatever gets the job done with main benefits of OSS being reviewing, extending, or just fixing things. A proprietary license allowing that has real value.
Curious, do you write comments like this whenever Google, Amazon, deep learning, etc closed-source tech with benefits are mentioned on HN? How they're insanity and not worth further discussion because the whole stack isn't FOSS?
- vitno 11y ago> Curious, do you write comments like this whenever... Uh.. I actually often do. I would more, but it generally isn't appreciated and is off topic of the main thread. Here, the software license is a key component of the release seeing as it is a unique component of it. >Open source is about the source being open plus certain benefits. It's more than that. The key intent of OSS is the right to study, change, and distribute the software to anyone and for any purpose. The source code is just a prereq for that ability. I did initially use stallman-esque language, since it's terminology most people are familiar with in this field, but I'll approach it from a different point since I personally have problems with strong copy-left licenses. The primary thing this license doesn't do is allow distribution in the OSS spirit. This is really just a pervasive license, actually in some ways similar to the Stallman-esque virality except with a corporate intent. It simply masquerades as OSS.
- nickpsecurity 11y ago"The key intent of OSS is the right to study, change, and distribute the software to anyone and for any purpose. The source code is just a prereq for that ability." No, the key intent of open-sourcing software is to let one see the source. That's it. Additional intents are added with licensing terms. This goes back to academic and even proprietary (eg Burrough's 1960's MCP) examples that did this. Many models of it formed with examples ranging from permissive BSD to proprietary OSS like LISP machines (esp Genera) letting customers use the source of OS & supporting libs in applications. So, OSS is a broader thing than you are describing which supports many models. There is no "spirit" so much as many different ideologies competing and pushing their own licensing schemes with various perceived benefits. Now there's one more.
- yarrel 11y agoThis is not Open Source, and trying to ignore the historical meaning of the term doesn't make it so.
- nickpsecurity 11y agoI just cited history rather than ignored it. That included Burrough's and LISP machines as examples past my linked essay in this thread. However, your side is ignoring all historical examples of proprietary OSS and even how non-proprietary OSS operated then vs now. Old model of academia varied from MIT/BSD-style to paid w/ source model. So, your rendering of open-source history is false both in academia and commercial sector. It's always been a mix with proprietary favoring closed source due to financial incentives, especially lock-in. Nothing precluded more paid OSS strategies aside from culture of organizations involved. As dual-licensed projects and proprietary w/ OSS benefits like this one show.
- davexunit 11y agoYou are incorrect. "Open Source" is a well-defined term. http://opensource.org/osd http://opensource.org/osd
- nickpsecurity 11y agoThe phrase itself originally came from the free software movement. The practice pre-dated it. Former is philosophical meaning with strings attached, the latter is a literal definition with many forms. I'm using the latter. I'd be up for considering a new term to avoid confusion. Paid, non-profit or for-profit, models allow for most benefits of OSS if structured correctly. So, the new phrase must allow for that. I've been calling it "proprietary OSS" or "paid OSS."
- davexunit 11y ago>Former is philosophical meaning with strings attached, the latter is a literal definition with many forms. I'm using the latter. You can't just change the meaning of the term and expect everyone to know you mean this alternate definition. "Open Source" is as defined by the OSI, and not whatever loose definition that you use that includes proprietary software. >I've been calling it "proprietary OSS" or "paid OSS." "Proprietary OSS" does not make sense given the definition of OSS! The phrase you should be using is "proprietary software."
- detaro 11y agoAdditional counterpoint: Even FAQ below their license explicitly states that it is not an Open Source license... So even its creators don't consider it to be one. from https://fair.io/ https://fair.io/: > We invite the entire coding community to adopt our simple, standardized, proprietary license. > No. Unlike open source, Fair Source has a Use Limitation built into the license
- nickpsecurity 11y agoIt would just be their opinion on the term. They are probably saying it because they know many potential users will have assumptions about what open source means. They wisely avoided going head-to-head with those assumptions to reduce number of negative reactions like seen here in other comments. I contend that open-source has always been a mix of philosophies which originally included commercial variants. The reason those disappeared probably had a lot to due with the greed of the dominant companies in IT. More utilitarian owners or charters might have had different results. However, there's still companies doing proprietary w/ source code and dual-licensing of proprietary + OSS.
- davexunit 11y ago>Free and open source software, a la Richard Stallman, is a totally different thing with a philosophy akin to how a virus operates. Copyleft is not a virus. I'm pretty damn tired of this meme.
- nickpsecurity 11y agoIt replicates once it attaches to things. This is true even of distributing a large amount of non-free code while someone in organization unknowingly included a tiny amount of copyleft code. Now, FSF etc are usually more reasonable about enforcement and I doubt most would do more than ask it be removed if whole isn't GPL'd. The image fits the behavior of the code, though. Hence the meme. More accurate description is like an agreement many parties participate in with copyright used to seal the deal for current and future distributions. So, control-freaks enforcing ideology on improvements to what they create rather than virus. ;)
- dragonwriter 11y ago> It replicates once it attaches to things. No, it doesn't. > This is true even of distributing a large amount of non-free code while someone in organization unknowingly included a tiny amount of copyleft code. If a single work is distributed that is based on copyleft code (not a mere aggregation that includes copyleft code and other code), then not licensing the resulting work as specified in the copyleft license is a violation of the license of the copyleft code. But the license doesn't attach on its own to the work.
- nickpsecurity 11y agoNow, it's possible my memory is messing me up again or I bought into a false explanation of the legal issues. To be clear, your saying that my worry was inaccurate and one person including GPL code into a new, released version of a proprietary app doesn't require the whole, linked source of that app be released under GPL? That happening is very virus-like but if it can't then it wouldn't be virus-like.
- dragonwriter 11y ago> Open source is about the source being open plus certain benefits. Free and open source software, a la Richard Stallman, is a totally different thing with a philosophy akin to how a virus operates. This is all wrong. One: Stallman only advocates Free Software, not Open Source, and not "Free and open source". Open Source Software and Free Software are defined very similar in substance (by the OSI and FSF, respectively), what differs most substantially between the respective organization is the philosophy of why they think those definitions are desirable, not the substance of the definition. Virtually all licenses that have been considered by both the FSF and OSI have either been recognized as meeting both definitions, or have been found to be outside of both; there's almost no inconsistency. "Free and open source software" is a collective term for the common category of software described by the FSF and OSI definitions, typically used by people who are not interested in (when using it) diverting things into a philosophical debate over preferred terminology between "Free Software" and "Open Source". The license type sometimes described as "viral" espoused by the Stallman and the FSF is copyleft license, which is a kind of Free Software (and/or Open Source) license which has clauses to assure derivative works are licensed under a similar license; the GPL and AGPL are well-known copyleft licenses.
- nickpsecurity 11y agoAnother commenter countered me on that and I agreed with the modification here: https://news.ycombinator.com/item?id=10623006 https://news.ycombinator.com/item?id=10623006 Any suggestion for what to call (a) software with source included in general that doesn't meet OSI & FSF definitions or (b) paid software w/ key benefits of OSI?
- dragonwriter 11y ago> Any suggestion for what to call (a) software with source included in general that doesn't meet OSI & FSF definitions "Source disclosed" or "Shared source". > paid software w/ key benefits of OSI? Since Open Source (and, for that matter, Free -- which means libre, but not necessarily gratis) software can be paid, if paid software actually has the "key benefits" of Open Source, it is probably because it is Open Source.