15 ms·
The culture war at the heart of open source
- kbenson 8y agoNot through yet, but small suggestion: > I’m not here to argue if the FSF has accomplished this goal You reference the FSF here, but introduce it with its full name in the next paragraph. I assume that's because you moved stuff around slightly in editing. It's a small thing, but it's slightly weird seeing it used and then introduced afterwards.
- steveklabnik 8y agoWhoops, thanks! Will fix.
- smush 8y agoThis argues for a third counterpart to FSF-style "Free Software" and OSI-style "Open Source Software" terms. Apparently, FSF is too preachy and OSI is too business-y and thus following "those who forget history are doomed to repeat it" style, a new, third movement of producing software that is free to copy, free to modify, etc. will naturally arise on its own. There are allusions to brogrammers who know nothing more about OSI than 'It's on GitHub!!', I'm not sure how charitable that is but I can say for several years that no matter how many wiki walks I've taken down the history of Linux, GNU et al which is probably where some of those brogrammers fell as well. IDK the difference, does it really matter, might as well stop looking into it any further than that. The schism and lack of unity between church of FSF and church of OSI has probably had a net detracting effect on getting software to be more permissible, even if the absolute effect has been way more FS/OS software than would be expected otherwis. I could be totally wrong, I didn't show up for computing until the Win 95 days.
- steveklabnik 8y agoThanks for reading! > a new, third movement of producing software that is free to copy, free to modify, etc. will naturally arise on its own. I think this is a bit too teleological. I'm not confident that such a thing will happen. I think that the environment is ripe for something to happen, but I don't know what that is. That's exactly because of > IDK the difference, does it really matter, might as well stop looking into it any further than that. I don't think that most people's conception of open source matches the FSF/OSI definitions. Does it really matter? I don't think it does for most people. I do think there's a values mis-match there though, and that means there's the possibility for a new thing that's a match. I think there are significant obstacles to that project, though. That's for the next post. I hope that I actually write it though, I've been trying to for over two years...
- AWildC182 8y ago> I don't think that most people's conception of open source matches the FSF/OSI definitions. To be honest, I'm still not sure what people think OSS is. I personally align heavily with the FSF model but that's mostly because I live in an industry (embedded) that obsesses over proprietary everything and thinks their shitty source code is the apex of valuable intellectual property (\rant) but I get that the story is very different on the other side where everyone is publishing Yet Another Javascript Library. Maybe this is all just a product of our environment?
- steveklabnik 8y agoI don't claim to know exactly either, and maybe you're right, and I'm over-correcting based on my environment :) But I have had a lot of conversations about this in the past few years... (I personally prefer the FSF model, but think that the OSI has won, at this point. All my software is Apache2/MIT these days. And even though I prefer it in the abstract, I have a lot of criticisms of both.)
- AWildC182 8y agoI think I forgot who I was talking to for a sec... I'm guessing there's quite a bit we agree on :) Looking across the aisle, I do wonder from time to time if the AGPL was a sort of breaking point. GPL always "threatened" industry at the desktop level and lower but once everyone's beloved FAANG+/- was in the cross-hairs the discussion maybe degraded a bit.
- steveklabnik 8y ago:) I think so, but I tend to think of it as not the AGPL's fault, exactly. That is, the GPL was a product of its time: it's very concerned with the details of writing non-networked C code. It pre-dates the web! It was impossible to forsee these kinds of changes, and it just so happens that it was not really prepared for them. The AGPL was an attempt to plug that hole, but it was too little, too late.
- zanny 8y agoI get the impression that the Rust community is wholly burdened in this third wave mindset. Everything is dual licensed Apache / MIT to guarantee maximum developer freedom. There have probably been a billion man hours poured into developing the Rust ecosystem at this point and I personally really think its destined for greatness. But the licensing style is already coming back to haunt all the projects - with growing popularity game studios, big megacorps, Mozillas own competitors, etc have started adopting Rust. And they give nothing back. No money, no developer hours. They take the fruits of a fledgling ecosystem and experience great productivity and performance improvements in their commercial products and reap increasing profits on the backs of people who naively just thought "I just want people to be able use my code is all". The third wave does not recognize the tremendous costs associated with giving away productivity to corporations. It costs society broadly, because it empowers business interests to exploit workers and customers for greater revenues not through their own ingenuity or innovation but through the labors of others given away freely. That isn't being generous on the parts of the developers who wrote the code for those that most need generosity.
- steveklabnik 8y agoSeveral of our production users do give back developer hours. Some have asked to give money, but we don't have a way to do it yet. We're working on it... > The third wave does not recognize the tremendous costs associated with giving away productivity to corporations. I think they do, and that's where the unrest is coming from. This realization has come after, not before, actually contributing.
- carapace 8y agoI'm a Free Software fanatic. I've often thought of getting a shirt that just says "STALLMAN IS CORRECT" in big block letters, so people know where I'm coming from. (As an aside, FWIW, the Open Source movement looks, to someone like me, like a largely-successful campaign to undermine the ideology that inspires RMS. But that's beside the point I want to make.) To me, the current economic systems (left, right, center) are all sub-optimal. I assumed automation would obviate most human labor and usher in a kind of Golden Age (cf. Bucky Fuller, et. al.) Instead, we have pocket computers that serve as strip malls and surveillance devices. (I'm in SF, where we have people living in tents in the shadow of shoddy "luxury" condos. This is hella dystopian y'all.) To someone like me, if you're programming a computer and NOT working towards a post-historical techno-utopia then you're kinda part of the problem. We have split the atom: no one should go hungry anymore. Blah blah blah, RepRaps, blah blah, universal basic income, blah...
- basementcat 8y ago> I'm in SF, where we have people living in tents in the shadow of shoddy "luxury" condos. This is hella dystopian y'all. Why is it dystopian? Some moral and economic systems value individual distinctiveness. What better way to express this distinctiveness than one's choice of living arrangement?
- mindslight 8y agoPresumably the people in tents are not choosing "I want to camp in an urban environment", but rather "I don't want to run on the financial treadmill" [0]. As that makes them useless to the financial treadmill, it is setup so they fall off the back hard and serve as an example to everybody else to keep running. [0] That is to say, to the extent that the houseless can actually be considered making a choice, or at least having made that choice in the past and are now stuck on that path.
- jasonmp85 8y agoWhat.
- ragebol 8y ago
- 0x8BADF00D 8y agoJust call the next movement The Entitled Software Foundation. Freetards begging for features and not giving back in any way whatsoever.
- steveklabnik 8y agoOut of curiosity, what projects do you maintain?
- 0x8BADF00D 8y agoNone, there is literally zero incentive to do so. All you will get is people complaining on your issue tracker, PR comments, etc. It’s better to write your own software and never release it to the external world.
- steveklabnik 8y agoDo you use any free software though? Ever file a bug yourself? I'm trying to see where you're coming from, but it's a bit difficult.
- 0x8BADF00D 8y agoI have contributed a long time ago, before Github and recently. My point is that the incentive structure doesn’t align with the amount of effort that’s required. You’re better off building something somebody needs and selling it. No reason to open source it, because the incentives are actually disincentives.
- meditate 8y agoBelieve it or not, but that type of community management is enjoyable for some and is incentivized to convey real benefits in both the social and financial sense. Also, even if you don't open source things you will still get users begging you for free handouts and unrealistic features. It's part of the business.
- mapgrep 8y agoHas Hacker News ever considered a policy against undated articles? I have no idea when this was written. It uses the word "today" four times and is written in the present tense but is it referring to events as of a day ago, a month ago, a year ago, a decade ago? Please put dates on your articles. Otherwise they read as spam, cynically positioned as "evergreen."
- TAForObvReasons 8y agoHighlight the title and the date shows up "MARCH 26, 2019"
- steveklabnik 8y agoThe date is literally the first text in the article, though it is a very light gray. Hovering over it or the title makes it black. This is Svbtle's decision, not mine.
- jah6q 8y agoOn my monitor that is nearly invisible
- duado 8y agoWhat an idiotic hosting platform.
- steveklabnik 8y agoI really like it, personally. It has some flaws like anything else, but overall it works well.
- Sir_Substance 8y agoIt's not in my browser. I guess it's loaded in from a script somewhere. The text loads fine without scripts but the date requires javascript to load. What an odd framework.
- judemelancon 8y ago
- billfruit 8y agoI do think there is a left vs right type of conflict between FSF and OSI. Esp Eric Raymond is appears firmly to be a partisan right winger, remember the very political things he tried to get included into the Jargon File some years ago.
- steveklabnik 8y agoI agree with you, and it partially informs where I'm going with this. I think the FSF is liberalism, and the OSI is libertarianism, more than a left vs right thing, exactly.
- mattnewport 8y agoLeft vs Right doesn't seem like a very helpful distinction to me here (but then I don't think it's a very useful way of looking at politics in general in the modern world either). The personal politics of some of the founding figures is perhaps helpful to understand the history but I don't think it's necessarily that useful in understanding the movements today.
- zach43 8y agoi could imagine a third camp between Free Software and Open Source following something like the Qt dual-licensing model: 1. You are free to use this software for non-commercial use. 2. If you'd like to use this software for commercial use, you must either actively contribute to this project, or provide a donation to the project maintainers at Patreon / Paypal / Liberapay, etc.
- pjmlp 8y agoThat is exactly my point of view. Want to use the work of others for free, then to you what others get. Willing to actually help upstream keep doing what they love, then great.
- fineIllregister 8y agoQt can be used commercially for free. It's LGPL whether you pay or not. Users only need to pay for a license if they want to distribute statically linked software with Qt, if it is licensed in a way that is LGPL incompatible.
- rrdharan 8y ago> Qt can be used commercially for free. It's LGPL whether you pay or not. This is true now, but was not always the case.
- empyrical 8y agoThe parent comment implied that it was still the case however, which is misleading; it has been available under GPL rather than the non-commercial "QPL" since 2000, and under the less-restrictive LGPL since 2009. Qt is also interesting in that there is also an agreement in place with the KDE Foundation that ensures that the Qt Company will always offer the core parts of Qt under a "proper" open source license. If they choose to switch to one of these non-commercial licenses again, then KDE is entitled to release the source under a BSD license if they want https://kde.org/community/whatiskde/kdefreeqtfoundation.php https://kde.org/community/whatiskde/kdefreeqtfoundation.php
- Stranger43 8y agoWhat we are seeing is not as much a war inside the community but an assault from a set of corporations that want to harvest their ownership of a name associated with a successful opensource project into making them the next Microsoft as they have to repay their investors/owners with super-normal profits a functional free market cannot actual provide. All of the recent issues have started with someone trying to reinvent Microsoft shared source idea where the focus is on code transparency not the right to modify and fork. It's a common pattern of substituting the real movement with a cargo cult copy, where the original goals is replaced by a set of consumable you have to buy, that have killed far more important movements then the opensource one in the past where orithe attack does not come openly but as astroturfing campaigns crafted to subvert real criticism and create the impression that the purveyors of cargo cult movement is trying to save the movement where as the goal is usually to carve a way for them to generate the cash their investors/creditors demand if not to become filthy rich. The opensource schism between osi and fsf was more about letting opensource escape the leadership by committee culture of academia and find a way for it to ride the corporate beasts as a symbiotic parasite through forking and re-merging. Where as the current manufactured crisis stems from the need of a bunch if startups to turn the relationship around and control the opensource project they back like a rider controls a horse which means preventing forks and independent commercial contributors. The Linux project where nobody uses the mainline kernel tree directly in production is a good example of the OSI model, here we have a bunch of companies forced to provide code upstream in order to provide a Linux product downstream to their customers in a relationship where there is not a "Linux inc" monopolizing the revenue stream generated from the end users but where all of the commercial contributors gets the revenue from their individual customers. What the likes of elastic or mongo that have been the center of controversy recently want is to become that single entity monopolizing the entire revenue stream of the opensource project they sponsor, which was also what oracle tried to become for MySQL and OpenOffice, as this is not an new conflict.
- steveklabnik 8y agoThanks for this comment! I think that your sentiment is not unusual, and exactly is what I'm talking about. I'm not sure I fully agree with everything you're saying, exactly, but I do think that it's a good illustration of how things, as they are, are not working for everyone.
- mindslight 8y agoThe point of "open source" was pragmatism over strict ideology, but then the ensuing vulnerability was exploited by DRM/SaaS. The sheer amount of "open source" today is because it is a great marketing term for what is effectively proprietary software or feedstock for proprietary software. It's not popular culture due to its empowering users, or even the pragmatism of say being easier to debug, but because it is the specific technology that Surveillance Valley businesses are built upon! Furthermore, dumped-over-the-wall projects like Android would be better referred to as "Shared Source" (with its association) - the Free branches are seemingly unable to actually keep up with the master! I think the answer to the conundrum is still "Free Software", but IMHO the FSF needs a strong makeover. On fundamentals, Stallman was and continues to be very much correct. But he seems to have become less applicable due to not necessarily choosing the right battles or making the right compromises. Here (https://news.ycombinator.com/item?id=19436615 https://news.ycombinator.com/item?id=19436615) is a thread I wrote a few days ago expanding in the specific context of firmware blobs.
- marknadal 8y agoYour claim that OSS is effectively proprietary software immediately loses half your audience, because most people in the OSS camp have the opposite experience (that FSF leads to monopolistic SaaS companies spying on you). I'm not saying either tribe is right, so let's skip past the tribalism. What we need is not new OSS/FSF, what we need is new economic models that are capable of measuring the value of OSS/FSF. Here is an extensive treatise to fix all of this: https://hackernoon.com/wealth-a-new-era-of-economics-ce8acd785441 https://hackernoon.com/wealth-a-new-era-of-economics-ce8acd7...
- mindslight 8y agoI wasn't saying that OSS is itself equal to proprietary software, but that it often ends up affiliated with non-free products. Products which then shamelessly continue using the OSS image to foster goodwill, even though their end users are far from having Freedom. > that FSF leads to monopolistic SaaS companies spying on you Erm, what? Both BSD and GPL software are similarly vulnerable to being transmuted into SaaS. This isn't an argument about specific licenses per se. What I'm calling out is "openwashing" in general. The FSF at least has an intellectual framework to analyze this. You don't need to license your work as GPL, but you do need to think ahead about the users of your software. Imagine using a derivative of your own work, suffering an annoying bug that you know precisely what it is, and yet being unable to fix it because a middleman has prevented you from doing so.
- nycticorax 8y agoI could have used some examples of "the war" in progress. Personally, this war has not really impinged on me. I'm not claiming it's not happening, but it would be good to have some evidence that it is happening. Or that the war has gotten hotter recently. Also, I have to say that I think it's a mistake to view "open source" as solely motivated by commerce. One big practical difference between FSF and OSI is how accepting they are of permissive licenses like BSD and MIT. Basically, OSI likes them and FSF doesn't. (Or at least FSF prefers copyleft licenses like GPL.) It's true that permissive licenses are more commerce-friendly, but one could also argue that they are more freedom-friendly as well. After all, with a permissive license, you can add your own proprietary extensions to a codebase and then sell the resulting executable without sharing the source for the extensions. With copyleft licenses, you are restricted from doing this. Thus permissive is arguably more free-as-in-freedom. Of course, copyleft advocates argue that copyleft licenses are more free in a larger sense, in that they guarantee that the code stays free. And, you know, maybe they're right. But I think it's something that reasonable people can disagree about. Whereas a lot of copyleft advocates seem to think that permissive licenses are a sign of moral weakness. I would say the permissive licenses are "free" in a libertarian sense, and the copyleft licenses are "free" in maybe an anarcho-syndicalist sense. It seems like a lot of people are convinced that copyleft licenses are more ethical than permissive licenses. I'm afraid I just don't agree with this.
- orangeshark 8y agoThe preference for permissive licenses vs copyleft license depends on where you value the freedom. As a developer who wants to write software, you might prefer permissive licenses because you have the freedom to do whatever you want with the software like including it in your propreitary software. As a user who ultimately runs the software, you might prefer the copyleft license because you get those same freedoms as the developer. I would admit that whether a user uses software that uses a permissive or copyleft license, it is pretty much the same.
- m0llusk 8y agoAnother view is that this has to do with how projects are managed. It is common to provide access to sources. Accepting submissions of changes to add features or fix bugs depends on who considers them to be improvements and why. If you want to really own a problem and cannot get the managers of the project to accept your changes then you need to fork. This issue exists with both free and open source but ownership is more directly asserted with open source. Saying this is money does not seem to mesh with the world we live in where RedHat provides services with free copylefted software valued at billions of dollars. Free copylefted software is big money now for better or worse.
- type0 8y ago> I think we’ll end up with a new movement. For the same reasons that “open source” came up with a new name, I think the movement that will arise from today’s developers will also need a new name. The name is source available and you don't need to have a movement for that. I don't see any schims here, essentially it is a more transparent version of freemium where you also can see the code and that's all decades old.
- stcredzero 8y agoThe name is source available and you don't need to have a movement for that. I don't see any schims here, essentially it is a more transparent version of freemium where you also can see the code and that's all decades old. Source transparency? Maybe we can popularize the idea that it's considered an altruistic act for tech media companies to escrow their source with academic organizations? This would help academics and museums preserve the exact media experience of each generation. From the article: Somewhere along the way, Open Source ran into a problem that many movements face: the members of the movement no longer understood the ideology that created the movement in the first place. Why shouldn't the values change? If people share source for prestige/recognition, to benefit from "more eyeballs" and to share the maintenance expense of shared infrastructure/libraries -- what's wrong with that? Society still benefits. The world isn't the same place where Stallman first thought of GNU. Why should the exact same ideology apply? What's wrong with some evolution?
- int_19h 8y ago"How could you treat a culture as separate from its connections? How could you draw a circle around it and say, “This, this is the culture, and so it will remain?” A culture wasn’t a final product, like a cup of coffee in alabaster, or a sordid climax in an execution alley. People didn’t have culture, they did culture. In fact, culture was like a mill: it accepted knowledge and people, and it changed them in certain ways, and it even redesigned itself in the process. Change was intrinsic to culture."
- droptablemain 8y agoHow did this guy manage to write an entire article on GNU, the FSF, and ultimately open-source, without once mentioning Richard Stallman's name?
- AceJohnny2 8y agoBecause it's irrelevant to the point of the article. It's not about who or the minutia of what happened (what!? no mention of the printer driver!?), it's about the driving principles and the landscape we have today.
- droptablemain 8y agoUmm, generally speaking, it is a common courtesy when quoting someone -- for example -- several blocks of text from Stallman, to at least mention their name. Meanwhile, every founding member of the OSI is mentioned.
- steveklabnik 8y agoBecause: 1. I tried to write the article without mentioning anyone's name. 2. I didn't like it as much as when I quoted from particular sources, so I started putting names in. 3. Personally, I am more sympathetic to RMS and more biased against esr. I really, really struggled to actually link to esr in this piece, but in the end, decided it was right. But I just didn't think about Stallman. My desire to work against my bias ended up just biasing my work. Writing is hard.
- droptablemain 8y agoFair enough.
- AceJohnny2 8y agoI know I've grown old when this history and the nuance of the open source concepts need to be spelled out for a new audience. Just some self-reflection. Thank you very much Steve for doing so in your usual engaging style.
- steveklabnik 8y agoThanks so much!
- platz 8y agoThis is why the GPLv2 doesn't only require the source code itself. You have to be able to effectively make use of that software freedom. It doesn't matter so much if you had software freedom, if all you had was the freedom to study, which is only one of the four freedoms. You need the freedom to modify, and freedom to install modified versions, and the GPL guarantees that. Question: How many IoT devices out there are running GPL'd firmware, providing source code, but no method to actually modify the device (or the current method is unmaintained and broken)? Answer: A lot! If you can't request sources and build & install them, it's a GPL violation. Rebuilding and reinstalling linux on IoT devices is a necessary step towards privacy and security on those devices.
- ryukafalz 8y ago>This is why the GPLv2 doesn't only require the source code itself. You have to be able to effectively make use of that software freedom. GPLv3 is intended to be better at this than GPLv2, specifically the anti-tivoization bits: https://www.gnu.org/licenses/rms-why-gplv3.en.html https://www.gnu.org/licenses/rms-why-gplv3.en.html
- spenrose 8y agoKudos to Klabnik for quoting from original documents. As he notes, Free Software is a complex phenomenon, and I respectfully submit that he doesn't do justice to the seeds-of-its-own-demise nature of its founding. My account, based largely on Sam Williams' outstanding Free as in Freedom: http://www.sampenrose.net/tools/ http://www.sampenrose.net/tools/
- jchw 8y ago(I'd like to note that most of these thoughts that follow are not directly tied to the article or aimed at Steve Klabnik; the article is good but it doesn't seem to make an assertion about what's right or wrong.) I still hold strong that this "war" is getting silly. This whole thing seems so antithetical. Open source is being chosen by developers and startups because it has technical benefits, it's appealing, it attracts attention, etc. The reason why it is all of those things is exactly because of what open source is. If you control the monetization strictly, it's not open source, and it loses the appeal. Simply having source available isn't appealing to me. Contributing to a project like that is just free labor. I see few mutual benefits. In my personal opinion, SaaS is not exploitation. Being able to do this is the point. The difference today is that there are people releasing software as open source under licenses that permit others to monetize their software... and then are shocked when they actually do it. Last time I made this argument, I mentioned Linux, and being the quintessential open source project it's a super good example of how open source can be collectively beneficial. I stand by this, and I would presume Linus is not bothered by the massive monetization of Linux. Since that's the point. If someone wants to build proprietary software, please do. The open source community can survive without another NoSQL database, I'm sure, and nobody will blame you. Few will do this, though, because many want to eat their cake and have it too. Whatever. In any case, please don't attempt to conflate "open source" with "shared source" in the meantime. I've said it before and I will say it again: You aren't saving open source. You are saving your profit model. And nobody blames you for that. I say this as a continued user of Caddy, Redis, etc. Disclaimer: I'm an employee of Google, these are my personal opinions and not those of my employer. P.S.: Steve, I'm really curious about that Gender bit. Are you going to clarify your thoughts on that?
- 0815test 8y ago> Steve, I'm really curious about that Gender bit. Are you going to clarify your thoughts on that? I'd like to know as well. Most others here have suggested that it's a veiled reference to "techbros" supposedly taking over the FLOSS community in the 2000s and 2010s, but that's both silly and would not represent a change in gender anyway, but rather a shift in broad social attitudes (including those relating to gender) away from the traditional hacker-values of openness and personal autonomy.
- zzzcpan 8y agoBusiness friendliness is not an ideological choice. Maybe a careless choice or a calculated one. But I don't think anyone has strong beliefs in it. Hence, the OSI side is fighting with an agenda. FSF, on the other hand, is ideologically strong, people hold genuine beliefs and fight for those beliefs. Well, not lately. As it turns out, FSF is not ideologically strong enough to take on modern issues and is ok for companies to wrap and build around free software to offer it as services, but never release any of the supporting code, forcing users into a proprietary lock-in, because they cannot run similar services without all of that extra code. So, here we are, in a need for stronger ideology. And even though this is also agenda driven of smaller companies, startups trying to protect themselves from bigger companies, there is still a lot to believe in.
- sanderjd 8y agoI dunno, I believe pretty strongly that it is a good thing for software businesses to be able to prosper. If that's not an ideology, I'm not sure how it is distinct from one. I don't think it's a careless choice; I've thought about it and actively concluded that I believe businesses are generally a good thing (note: not always, but generally). Maybe it is a calculated choice because one of the reasons I'm in favor of businesses is that they are how I employ myself and earn a living. But that's not the only reason; I may work in the public sector one day, but in all likelihood I will still believe that businesses are generally a good thing. It's just a belief that I hold. Is that an ideology? I don't know, but it seems like it might be.
- jacques_chester 8y agoI don't think that's a fair statement of the FSF's position. From the horse's mouth: > Early drafts of GPLv3 allowed licensors to add an Affero-like requirement to publish source in section 7. However, some companies that develop and rely upon free software consider this requirement to be too burdensome. They want to avoid code with this requirement, and expressed concern about the administrative costs of checking code for this additional requirement. By publishing the GNU Affero GPLv3 as a separate license, with provisions in it and GPLv3 to allow code under these licenses to link to each other, we accomplish all of our original goals while making it easier to determine which code has the source publication requirement. https://www.gnu.org/licenses/gpl-faq.html#SeparateAffero https://www.gnu.org/licenses/gpl-faq.html#SeparateAffero The "administrative burden" is not academic, by the way. Where I work we spend a lot of time and money checking that we are compliant with every license pulled in directly or indirectly into our products.
- peterwwillis 8y agoLots of words and phrases have their meanings change over time. That's not culture war, that's just... culture.
- steveklabnik 8y agoSure. The war is over which particular possible future meaning will happen, not over the concept of change.
- pixelmonkey 8y agoThe real amnesia about “open source” history is that, at the time of the formation of the OSI, developers and companies were afraid of Free Software, Copyleft, and GNU. Making free/libre/community code palatable — even merely for re-use — was an uphill battle. Nowadays, use of open source is so pervasive that you get a strange look in developer circles when you use the word “proprietary”. And we are worrying now about paying for committer/maintainer time given how important OSS modules are, especially standard and popular programming libraries and database technologies. That is quite the inversion. Let’s take an example: search. Elastic has gone public while employing an army of Elasticsearch and Lucene committers, and while selling SaaS and cloud services around Elasticsearch and related projects, thus paying for those committers, creating a massive ecosystem/community, and revenue for themselves (plus return for their investors). A win like that would have been unimaginable in the pre-OSI era. Companies wouldn’t adopt Elasticsearch, wouldn’t put real data in it, and certainly wouldn’t pay some company to run it for them. Instead, that era saw companies like Verity, FAST, Autonomy, and similar proprietary search engines. Can you even name a proprietary on-premise deployable search engine today? Even if you can, it’s probably powered by Lucene, Solr, Elasticsearch under the hood. That’s how much the entire universe has shifted.
- xkcd-sucks 8y agoWell shoot, putting it like that I wouldn't mind it if all the search engines were proprietary and well-documented so I wouldn't have to justify the cost against the less easily quantified cost of using Elasticsearch
- Jedi72 8y agoIf you want to box up the cost for accounting purposes why not just hire elastic search consultants? From the buyers point of view its not any different from a proprietary company
- int_19h 8y agoMany companies are still afraid of copyleft. When you see what actually gets used in corporate environments and shipped in commercial products, it's almost exclusively MIT/BSDL/AL, some LGPL, and very little GPL.
- m463 8y agoOne thing RMS has said is that Free Software (GPL) places no restrictions on how anyone USES the software. The rights reside with the actual users. The GPL does restrict how you REDISTRIBUTE it. If you modify the software, you must distribute the modifications when you redistribute it. Businesses that just use the software are fine with GPL. But businesses that want to redistribute GPL software cannot fork and close it. But they're businesses and have revenue, so they can pay others to use their software, or just use MIT/BSD licensed code that allows fork and close.
- mattnewport 8y agoI think the FSF philosophy has proved remarkably prescient. For a long time I didn't really get it and it seemed excessively rigid and unrealistic. So many of the dangers that I now see in the path of technology were anticipated in the founding principles and four freedoms however. I've definitely come round if not yet a card carrying convert.
- bitwize 8y agoThere's a whole subreddit called /r/StallmanWasRight so you're hardly alone.
- orangeshark 8y agoThinking more about the issues, it really seems this only affects a subset of software, specifically server software. A SaaS company won't be able to turn and sell some desktop software as a service. We sort of seen this in the past with hosting companies selling services with apache, php, and various other software together, but I guess the maintainers of these projects were not competiting in this area so it never mattered. I also find it odd that one of the reasons to use the term open source was because of the ambiguity with the meaning of free. Even with this reason, the majority of open source software is free/gratis. I agree with the problem we are facing now, we are just not educating many developers on free and open source software. It is probably something we need to improve on.
- mwfunk 8y agoI think there are 3 wars that overlap but not fully. (1) Pragmatic debates about the usefulness of copyleft vs. BSD/X11/MIT/etc. in various situations (and for various goals), (2) a (tribal, and mostly imaginary?) "business vs. hackers" narrative, and (3) RMS vs. everyone else. OSI itself doesn't figure prominently in how I think of open source. I realize Open Source^tm is something that OSI legally defines, but going all the way back to the endless Usenet arguments in the '90s, the "open source vs. free software" conflict was never really about OSI vs. the FSF (IMO). It was more about accepting a multitude of licenses as acceptable alternatives, vs. adherence to the strictest and most complicated one (plus accepting Richard Matthew Stallman as your personal lord and savior). It also felt like "open source" meant promoting a bunch of things as a common good, but "free software" meant promoting something very specific as good, and calling out a bunch of other things as evil. It's like working for a charity vs. being in someone's army. I wonder how much this contributes to which side is more appealing to someone, based on their values and personality. Maybe this has become way more convoluted since the '90s, but I always considered open source to be a superset of free software. All GPL'd software is open source, but not all open source software is GPL'd. It's less of an "x vs. y" conflict, and more of a "(x, y, or z) vs. x" conflict, with a bunch of cultural and personal baggage tacked on to it.
- caf 8y agoI was around for those arguments in the 90s as well, and that's not at all my take on it. The FSF was always very clear that the BSD-type licenses (at least once the minor issue of the "advertising clause" was dealt with) were Free Software licenses in their opinion. The Debian Free Software Guidelines always covered a wide variety of permissive "open source" licenses, and in fact the DFSG was used as the basis of the OSI's Open Source definition. So I've never seen Open Source as a superset of Free Software - or vice-versa. Rather, they have always been almost or even exactly the same set. It's not, and never has been, about alternative taxa - instead, the difference was always more one of marketing. It's not a question of What - it's a question of Why. The Why of Free Software is "So that people are free to share and modify the software they use", and the Why of Open Source is "Because this method of development creates better software.". If a new movement does crystallise, it will be because neither of these Whys satisfy the new constituency, and their new answer to Why Permissively License Your Software? will be their rallying point.
- yakshaving_jgt 8y ago> I’m not sure exactly how it happened. I think the lazy answer is “GitHub!!!!”. I do think GitHub played a role, but I think the answer is more complex than that. I personally think that gender plays a huge role. But that’s a different essay. Regardless of why it happened, something did happen. "GitHub!!!!" may be a lazy answer, but why isn't "gender!!!!" an equally lazy answer?
- steveklabnik 8y ago1. Gender is an extremely complex topic, "github made more devs" is not. 2. I didn't say that "gender!!!" was an answer; I said that the answer is complex, and that things like gender play one role in it. 3. I didn't give any answer here, explicitly, so it cannot be a lazy answer.
- bitwize 8y agoI think an even better lazy answer is "millennials!!!" Or rather, people who got into programming after The Cathedral and the Bazaar proved phenomenally successful at its job. Back in the 90s, free and open source software was obscure. The ideology really only appealed to people who were inclined to get into programming, and then only to a small subset of technolibertarians who valued the potential riches copyright could bestow less than they were irritated by the hindrance it presented to writing more cool software, or even to using a computer without frustration and risk. To such people, preserving and contributing to the canon of free software became an important cultural mission very closely tied with the concept of human freedom itself: if anyone with a computer is to be truly free of the predations of governments and corporations, they must be running free software, and inasmuch as people still can't do that for 100% of their uses for a computer, that's an open problem to be solved. These people are likely to be very conscientious (being programmer types) and to have actually read the GNU Manifesto, CatB, and related documents. These days, Raymond's message of "open source is good for business" is so accepted in the tech world that it's the first form of this ideology many (if not most) open source devs are exposed to. A lot of that has to do with the first, second, and third dot-com booms that open source helped to kick off, which vastly expanded the pool of developers and developer wannabes with the promise of startup-founder riches. The composition of people involved with open source has changed from "mainly hackers" to something including many more business types, who are far more "practical" in that they are concerned with the following quarter's bottom line (or their own paycheck) much more than any ideology. So they understand that open source is good for business, but do not comprehend the relationship of free software to individual freedom and society as a whole. They are concerned with what's good for business. And if closing the source partway or all the way delivers higher projected revenues over the next fiscal quarter or year, so be it. That's a sacrifice they're willing to make. It's unfortunate that we haven't communicated our values to the wider community nearly as effectively as Stallman or Raymond might have hoped. Comfort can be taken, I suppose, that we are still better off than we were in 1995, when software development was 99% proprietarywith expectation of payment, and giving your software away meant you were either some sort of communist, or didn't value what you wrote too much.
- femto113 8y agoI remember in the early days of JPG some people claiming that despite the size advantage GIF's image quality was inherently better and should be preferred. One JPG fan wrote something that really stuck with me: "I don't know which is 'better', but I know I'd rather have 10 of these than 2 of those". Software developers are, as a rule, lazy. We pick "free as in beer" software because it means we don't have to figure out how to get accounts payable to approve it. We pick MIT licensed software so we don't have to figure out how to get the lawyers to approve GPL. And we publish stuff on GitHub with random new licenses because it's so easy to do. In the end I would rather have 10 such projects to cull code and ideas from than 2 that had carefully articulated ideologies that provided clear motivation for each clause in their license.
- otikik 8y agoI once met a lead who called Google "a bunch of hippies", because some part of their software was Open Source. His company had ~10 employees. We decided we were not a good fit.
- openloop 8y agoMIT. I don’t know.
- extreme_orang 8y agoWorth looking at these books in relation to this topic Copy, Rip, Burn: The Politics of Copyleft and Open Source: The Politics of Open Source https://www.amazon.co.uk/dp/0745324142/ref=cm_sw_r_cp_api_i_Ub4MCbBF31XWS https://www.amazon.co.uk/dp/0745324142/ref=cm_sw_r_cp_api_i_... Two Bits: The Cultural Significance of Free Software (Experimental Futures) https://www.amazon.co.uk/dp/0822342642/ref=cm_sw_r_cp_api_i_tc4MCbRPWHNJZ https://www.amazon.co.uk/dp/0822342642/ref=cm_sw_r_cp_api_i_...
- mcguire 8y ago"I’m not sure what that movement will look like, and I’ll explore why in another post. To give you a teaser: the problem is in the way that both Free Software and Open Source are formulated. The rot is in the roots, and I’m not yet sure what will replace it." Looking forward to it. In the meantime, consider a couple of kernels: Linux and sixth (or seventh edition) Unix. Unix wasn't released under a free or open license, but the effects were similar to an open source license: you could give away your changes if the recepient had an ATT license. The results were SunOS, Solaris, and other monstrosities like AIX, HP-UX, Irix, and a dozen others, all different enough to prevent compatibility and ensure lockin. This lasted until the Unix environment collapsed under it's own weight. On the other hand, there's only one Linux, under the GPL. There are forks, but few have real momentum. Major improvements are absorbed into the mainline kernels. Likewise, in the C and C++ compiler space, gcc (its internal bit rot not withstanding) ate all of the other options. You don't see the difference in most open source, possibly due to the momentum of Apache and Mozilla. Or possibly because most software has a short half-life. But see Amazon and Google's cloud support offerings. Licenses express ideology. Choose your roots carefully.
- pjmlp 8y agoAs additional note, gcc only picked up steam when Sun decided to start the trend of selling UNIX developer tools as an additional package.
- mcguire 8y agoI'm not sure of the chronology there; didn't gcc start when Sun started separately bundling development tools?
- pjmlp 8y agoNo, it preceededs Sun's decision by a couple of years. http://shape-of-code.coding-guidelines.com/2017/03/22/happy-30th-birthday-to-gcc/ http://shape-of-code.coding-guidelines.com/2017/03/22/happy-... http://www.groklaw.net/article.php?story=20050525231654621 http://www.groklaw.net/article.php?story=20050525231654621
- cheezymoogle 8y agoHistory doesn't repeat, but it certainly rhymes, so the saying goes. To anyone acquainted with the history of Christianity (or religion more generally) and the history of libre software, the parallels are simply fascinating. From the Book of St. IGNUcius, 12:1-12: Then began rms to speak to the people this parable; A certain person created a program for perself, and sent its code to other programmers, and went into a far country for a long time. When per returned, per sent an email to the programmers, now selling the software as a service, that they should forward any code that they had improved, so that other programmers might benefit from it: but the programmers ignored the email, and refused to acknowledge the debt. And again per sent another email: and they ignored this one also, and maligned per on other mailing lists, calling per greedy and envious for prestige, and still refused to acknowledge the debt. And again per sent a third: and this one, too, they ignored. Then said the creator of the program, What shall I do? I will send the code of my latest extension to the program under a copyleft license; it may be they will understand the obligation of using libre software and the reciprocal sharing of code when they read the license and modify the code. But when the programmers saw the new code, they reasoned among themselves, saying, this is a vast improvement on the original: come, let us obfuscate this code and delete the license, that we may continue to sell the software without giving back. So they added the code to their the program and deleted the license. What therefore shall the original programmer do unto them? Per shall come with lawyers and sue these programmers, and shall then give the source code to others. And when they heard it, they said, Google forbid. And he beheld them, and said, What is this then that is written, The license which the engineers rejected, the same has become the backbone? Whosoever shall fall upon that license shall be broken; but on whomsoever it shall fall, it will grind him to powder. And Silicon Valley and their coders the same hour sought to lay hands on him; and they feared the people: for they perceived that he had spoken this parable against them.