8 ms·
An open letter to Richard M. Stallman
- deleted 12y ago[deleted]
- CJefferson 12y agoThis is totally amazing, I knew that RMS used to hold this opinion (hiding the GCC AST so nasty people can't misuse it), but I believed (wrongly it turns out), he'd abandoned it by now. I can't see how he can defend crippling software, and blocking usecases which clearly a large set of users want (all kinds of editor intelligent colouring, competition), out of fear of a closed-source boogyman which doesn't exist any more, thanks to clang (if it ever did).
- TylerE 12y agoBecause Stallman has never given a fig for the users, just the programmer-gods.
- ralmidani 12y agoThe point of copyleft is to protect users from being oppressed by programmers.
- _ak 12y agoCopyleft is a collectivist ideology, it only ever cares about users as an anonymous mass, but not about individuals with individual needs and constraints.
- dalke 12y agoCopyright is also a collectivist ideology. "To promote the Progress of Science and useful Arts" is even more anonymous than "users".
- prodigal_erik 12y agoNo user ever needs to be unable to arrange for maintenance of the software they rely on. That only benefits some developers by holding their customers captive.
- smithzvk 12y agoThe other reply says as much, but it bears repeating as what you said is so extremely incorrect. The GPL is and always has been a license that limits the rights of programmers in order to ensure the rights of users. This is one of those, frankly, pretty rare cases where the users actually feel a limitation of the GPL (mostly because people that use Emacs has a significant overlap with programmers where the line between developer and end user is very blurry).
- TylerE 12y agoHow many non-programmer users do you personally know that are capable of compiling a C program from source?
- hga 12y agoThey could always hire other programmers to do that. And there's real value in having that option, or getting software from a community that works like that, most famously the Linux distro scene.
- djur 12y agoNot many people are capable of fixing their car personally, but they do benefit from not being required to go to Toyota whenever it breaks. Nonfree software is like an appliance which you're legally forbidden from modifying without permission from the original maker.
- smithzvk 12y agoMissed your reply. Actually it is pretty irrelevant how many non-programmers are capable of compiling or meaningfully editing the C program. The point is that a programmer cannot (reasonably) edit to restrict you freedom. However, after rethinking what I wrote, I should clarify that while the underlying principles are the same regarding what RMS is trying to do here (limit programmers to protect users), the GPL has nothing really to with this particular fiasco.
- belorn 12y ago> the rights of programmers So adding proprietary license on top of software which one has not authored is a right that belongs to programmers?
- yuhong 12y agoTo be honest, I think it was useful back in the 1990s.
- __david__ 12y ago> …out of fear of a closed-source boogyman which doesn't exist any more… (if it ever did). It most certainly did. Read here[1] about the history of Objective-C. NeXT tried to keep as much of it as possible proprietary. Sadly, because LLVM is so good but doesn't have copyleft protection, we live in a world where something new and interesting like Swift may never be non-proprietary. [1] https://en.wikipedia.org/wiki/Objective-C#Popularization_through_NeXT https://en.wikipedia.org/wiki/Objective-C#Popularization_thr...
- MBCook 12y ago> we live in a world where something new and interesting like Swift may never be non-proprietary. Should Apple not have a right to make their own proprietary language? Let's not forget that Apple is a big part of why LLVM is as well known as it is.
- jacquesm 12y agoProprietary language? You mean like a single platform language? What a complete waste that would be. Languages can't be proprietary, anybody can re-implement some language if there is a spec. Whether you can name it the same or not is another issue but non-proprietary languages usually don't survive for very long so it would be in Apples own interest that swift ends up in as many hands as possible. Oracle still doesn't understand this completely about Java, maybe Apple will never understand it about Swift, meanwhile all those non-proprietary languages will flourish.
- meepmorp 12y ago> ... proprietary languages usually don't survive for very long so it would be in Apples own interest that swift ends up in as many hands as possible. This is wrong thinking and it misunderstands Apple's goals and motives for Swift. First and foremost, it's a replacement for Objective-C, which is itself effectively proprietary - there are open source compilers and some legacy openstep implementations, but the driving force behind the language has been exclusively Apple for at least a decade now. In that context, Swift has the same expected level of success as Objective-C, owing to the community that exists around its predecessor. And, for Apple, the important metrics for success with Swift are entirely focused around the effectiveness of the language in support their platform. Given the relative popularity of the platform, they can reasonably expect that people will use the language to gain access to Apple's userbase, because it's a valuable commodity. Second, Apple doesn't care if Swift has a long life, at least, not per se. They want it to be used and to be successful because it's where they're probably moving their platform in the medium to long term. But they're not invested in the longevity of the language so much as they're invested in their platform. If, in another decade, they decide that Swift has outlived its usefulness, they'll replace it and let it die. Any other scenario for the language failing entails Apple faltering as a company, in which case, they don't really care about the Swift's success. (I snipped a "non-" off proprietary, because it didn't seem like what you were arguing from the rest of the post.)
- gillianseed 12y ago>out of fear of a closed-source boogyman which doesn't exist any more, thanks to clang (if it ever did). Eh, what ? Apple is already shipping their proprietary fork of Clang which supports their proprietary language Swift, this is exactly what Free Software which Stallman advocates is working against. The whole idea of Free Software is that the end user will have the full rights to examine, modify, copy, run said software, proprietary plugins in GCC flies right in the face of that, so obviously Stallman is opposed to them.
- anon1385 12y ago>Eh, what ? Apple is already shipping their proprietary fork of Clang which supports their proprietary language Swift, this is exactly what Free Software which Stallman advocates is working against. Thats exactly the point. Anybody wanting to make a proprietary language implementation, or proprietary IDE is already using llvm anyway, and would remain doing so. New projects of that nature would almost certainly still use llvm. The only people really being affected by this are people who want to use GNU tooling, but are left with deliberately crippled tools. The ability to develop plugins for GCC has existed for years now, but nobody has used it to do the evil things RMS insisted would happen (remember, he blocked the creation of the plugin interface for many years). The main reason is that Clang/LLVM is just much easier and nicer to work with (e.g. you don't have to write and maintain your own plugin to export an AST instead of having it be part of the core project). Hence all the brightest young minds in compiler research and language development are using LLVM in their work instead of GCC and an entire generation that could have been using and contributing to GNU software are working to improve 'the enemy'. Its hard to think of a more valuable group of people to drive away. Or a more thorough way to drive them away than to try to put intellectual shackles on them. Stallman's suggestion of only exporting a gimped AST that only allows a few specific transformations gives people involved in languages and tooling the same reaction as RMS feels when told he can't see the code for the software on his printer. >The whole idea of Free Software is that the end user will have the full rights to examine, modify, copy, run said software, proprietary plugins in GCC flies right in the face of that, so obviously Stallman is opposed to them. Nobody is proposing creating proprietary plugins for GCC. People are proposing a GPL licensed plugin to export the AST for use by emacs. No proprietary code involved at all. RMS has said he would block the use of such a plugin in emacs, thus deliberately crippling emacs, which is why emacs is probably going to get forked (again).
- forrestthewoods 12y agoIt feels like the influence of (L)GPL and perhaps even Stallman is almost at a close. These days I'm genuinely surprised if I see something new released under an (L)GPL license. And when it does happen it's often released under a more free MIT or BSD license soon thereafter.
- yuhong 12y agoI think the GPL is still useful.
- forrestthewoods 12y agoIt absolutely is. That doesn't change anything in my comment though.
- __david__ 12y agoYes, the grandparent is crazy to think the GPL isn't relevant. In certain circles it isn't as popular, the GP must travel in those circles. It's still wonderful to be on a linux system where I can just "apt-get source <pckage>" and look at how it works, try to work around bugs, etc. The attitude that you should be able to break apart anything you're running and hack on it is the fundamental principal of the GPL. I have a suspicion that people who dismiss the GPL nowadays are young enough to have never lived through the times where the standard unix server was running SunOS and good luck to you if you ever found a bug in the system. You know, the days where you had to pay for a (sucky) compiler.
- rdtsc 12y agoI think a lot of people are shortsighted and they sort of see the world immediately in front of their eyes. I am building a product, I need a library, GPL, fuck GPL! Gah, gotta search for a BSD one and curse GPL in the process. They probably never lived in the days before Linux, GCC and free software as something that can happen in reality. Yet looking back here we are. People sharing code on github, companies sharing their code (either licensed as GPL or other open source licenses). High grade languages, compilers, OSes, kernels, crypto libraries all free and/or open. I think that would not have happened had it not beed for Stallman and GPL. A lot of developers I find are also bored or ignorant to study or understand licensing. Concepts like "copyright", "license", "open", "free" are all confused and relegated to mumbo-jumbo legalese. Today most have internalized the simple heuristic "GPL" = stay the fuck back or our legal department will slap me on the head, "BSD" = good, use anyway you like.
- dmm 12y agoRMS doesn't care about "open source", something he will gladly remind you of if you use that phrase in his presence. His position in this matter is long-standing and consistent with his principles. That's how you have to understand him: a man of principles surrounded by enemies. Look at OS X, why does it use such an ancient version of Bash? Why is apple so afraid of the GPLv3? It's not just an oversight. The GPLv3 provides strong patent protection for its users and Apple uses patents as a weapon. An example of this powerful weapon was Apple's conspiracy to suppress wages by threatening companies who poached Apple employees with patent suits. Imagine you make a tool and someone proposes making a change to that tool that would be potentially useful to slavers, people who enslave other people. This makes you hesitate. Pointing out that people already use similar tools for slavery probably wouldn't make you change your mind.
- forrestthewoods 12y ago"enemies" or merely people who politely disagree with his definition of free?
- deleted 12y ago[deleted]
- krapp 12y ago>a man of principles surrounded by enemies. Or a zealot who sees enemies everywhere.
- asuffield 12y agoNeither of the above. It's no secret what RMS is doing here, and he's fully aware of the context and way in which he is perceived. Some people like to think that he doesn't care, and they have it almost exactly backwards. The most extreme person on any issue is always ridiculed and disregarded by a large chunk of any community, regardless of whether this is correct or not. People like middle things. RMS's objective is to be the most extreme person, and to drag that position so far over that no other free software effort can be ridiculed or ignored in this fashion. You haven't chosen to be the middle ground here. RMS has chosen to make you the middle ground, because that's where he wanted it to be, so he hiked all the way over there to plant his flag in order to move the middle. A few decades later, it looks like that worked.
- nullc 12y agoI see a thread were RMS seems unusually patient and polite: https://lists.gnu.org/archive/html/emacs-devel/2015-01/msg00162.html https://lists.gnu.org/archive/html/emacs-devel/2015-01/msg00... And a blog post by someone who's name seems to appear nowhere in the GCC SCM history, threating a fork. It's not clear to me whats going on here.
- mwfogleman 12y agoThe maintainer of Emacs, Stefan, actually started all of this forking talk.
- krig 12y agoI really don't think this is an argument that will convince Stallman. As stated, there have been forks of GCC (as well as Emacs) before. It's not as terrible a threat as it might seem.
- _ak 12y agoegcs was big enough of a threat that it became the official gcc codebase.
- gillianseed 12y agoegcs was free software working exactly as it should, you don't like the current direction, fork it, and thanks to it being copyleft the fork is entirely open and can later be merged back or as in this case, become the new official project.
- jacquesm 12y agoI don't think GCC is under any threat of being abandoned any time soon. The intended audience of an open letter is rarely the addressee and I don't think this one is an exception to that rule. It merely uses the name of Richard Stallmann to widen the exposure (apparently successfully so). If she wants to fork GCC she should go right ahead and we'll see if the dedication to maintain that fork over the next couple of decades is there or not. I don't think GCC has much to fear from such a development and possibly something good might come out of it if there is merit to her ideas or if the fork produces some other useful insight which can then be absorbed by the upstream. Usually such forks lead nowhere, every now and then the fork will blossom and ends up overshadowing the original, that's the whole power of free software right there. RMS is perfectly within his rights to decide the way he does (that's part and parcel of being a creative person rather than acting with some sense of entitlement about how others should modify their creation to suit your own intent) and bringing pressure to bear by attempting to gather a crowd that pushes for an issue is a low tactic.
- Gracana 12y ago> If she wants to fork GCC she should go right ahead She doesn't want to fork gcc. She's saying that if people wanted to use gcc in this way so badly, they would fork. But nobody is interested in doing that, because it's easier to work with clang rather than try to fight with gcc. And the argument is that gcc is worse off for having driven those users away.
- jacquesm 12y ago> She doesn't want to fork gcc. Yes, I got that. I'm saying that she should if she feels the issue is that important (assuming she has the skills to pull off the fork). > She's saying that if people wanted to use gcc in this way so badly, they would fork. Conclusion: they don't. > But nobody is interested in doing that, because it's easier to work with clang rather than try to fight with gcc. That's most likely not a majority of the users but if clang serves their need that does not diminish GCC in any way other than that a couple of users moved to a different product. Big deal. GCC does not charge any price of admission, you are free to use it and you're free not to. If you're not driving the car you don't get to shout from the sidelines on what direction to take. > And the argument is that gcc is worse off for having driven those users away. GCC (and by extension Stallmann) are not driving anybody away. If you feel 'driven away' because someone does not act as you think they should then you have an entitlement problem.
- tatterdemalion 12y agoI am a strong supporter of the GPL and its relatives, and of copyleft free software in general. Clang is going to replace the GCC in time because of the superiority of its design, and I think it's a shame it's not under the GPL. But I think RMS is wrong here. I would never initiate a free project under a license that isn't strictly copyleft, but I also would never intentionally limit the usefulness and expressiveness of a program I created because that output could be useful for non-free software. If he doesn't want the GCC to be useful for non-free software, why is there language preventing compilation from falling under the linking clause of the GPL? Maybe I just don't have a strong enough understanding of the context here. That said, this "open letter" is quite absurd! Not even getting into the really dubious substance of it: why such hostility? why such trumpeting? why not respond on the mailing list?
- ForHackernews 12y ago> I think it's a shame it's not under the GPL. If Clang is under a permissive non-copyleft license, can't you just fork/relicense it under the GPL? And then build improvements on the GPL version? It's not very nice or sporting, but counterintuitively, it would help demonstrate why copyleft is important.
- profquail 12y agoI'm not a lawyer, but from what I understand - you can't simply re-license the existing code, because the copyright does not belong to you. You could add your own GPL-licensed improvements to the code though, in which case consumers would need to abide by the terms of the GPL (because they're consuming both the original BSD-licensed code and your GPL-licensed code).
- zanny 12y agoIt is MIT based, which is GPL compatible, so yeah, you can make GPL only changes in your own Clang fork and if anyone uses your changes in their own Clang fork regardless of what all the other code is licensed under they are now beholden to the GPL. Which is why I really don't get the doom and gloom around GCC here. Architecturally LLVM makes huge sense. If you are a free software advocate it makes all the sense in the world as well to continue developing GCC until such a time where the technical merits of LLVM are too great to ignore. And then you just release GNULVM as a fork of LLVM under the GPL and continue on your merry way. Merge in all the good stuff from GCC and upstream patches from LLVM into your working tree and get the best of both worlds, because as long as new contributions are GPL you are not enabling the deprivation of user freedoms.
- jakobegger 12y agoSomething interesting has been happening in the Open Source world. In the beginning, open source software was developed mostly by academics and free software advocates. Copyleft licenses like the GPL became very popular as a means to prevent for-profit companies from using all this free software without giving back. There seemed to be a struggle between closed source proprietary software, and free open source software on the other side. The lines have blurred, and now a lot of open source projects are developed and maintained by for-profit companies. Projects like clang, SQLite or PostgreSQL are all developed mostly by profit-oriented companies. These projects use liberal licenses; they aren't interested in "protecting" their code -- for these projects, the situation is actually reversed. Proprietary software vendors make large parts of code freely available to the world! Maybe this is a result of the GPL; evil corporations are afraid of the GPL and therefore they support projects with liberal licenses. But maybe the GPL is just not necessary anymore; companies see the inherent advantages of open source and make (some) code available even without the GPL gun pointed at their head. What a wonderful world this would be! The GPL always seemed like fighting fire with fire. Maybe the world is better than we thought.
- jacquesm 12y ago> The GPL always seemed like fighting fire with fire. That's exactly what it is. You have to really appreciate the care that went into drafting that, if there ever was a real-world hack the GPL would be it.
- Nelson69 12y agoThere are a fair number of interesting PostgreSQL forks that are completely proprietary. Those guys DO care about their source code. That's the exact case GPL is designed to protect against, there are developers that contributes to PostgreSQL and cannot use that code. There does seem to be an overall shift and source code isn't seen as it once was but there is no shortage of companies that would gladly keep "their secret sauce" secret. How many web services use tons of opensource and short of reading their obfuscated javascript from their web pages, do they make the source available? And realistically, it's data and the service that is their edge. Take github for example. RMS comes across as a bit extreme at times but we are where we are in part because of him.
- deleted 12y ago[deleted]
- biggot_man 12y agoDid you actually try to send him an e-mail ? He usually answers in a timely fashion. Or are you just doing this because you need some attention ?
- omouse 12y agoThere's a difference between creating something and then also promoting it. The FSF and the GNU project shouldn't encourage the creation of the plugin and they shouldn't promote it. However, they cannot stop anyone writing the plugin that exposes the AST in such a way to be usable by proprietary programs. The Emacs project also shouldn't promote this project. This is exactly similar to how FSF and GNU don't promote the Windows version of Emacs. They don't hinder it or stop it, but they don't promote it or mention it either. I think the Emacs maintainer blew things out of proportion and so has everyone else.
- bjornsing 12y ago> However, they cannot stop anyone writing the plugin that exposes the AST in such a way to be usable by proprietary programs. I'm not entire sure they couldn't... It really comes down to the definition of a derivative work. It's often assumed that a process boundary would somehow raise some legally impenetrable wall between works, but I'm not sure a court would necessarily agree.
- hga 12y agoRMS would very likely respond to this by frequently changing the plugin interface and updating only the blessed plugins. Linux is not entirely dissimilar in how it does device drivers.
- mehrdada 12y agoThis argument is based on the assumption that LLVM is equivalent to GCC. If that were true, it wouldn't have really mattered that GCC exists or what it does and the argument wouldn't have been made in the first place. The fact that this argument exists undermines itself.
- hga 12y agoThey're not equal from the viewpoint of the FSF, and since this is an issue about FSF Gnu EMACS using such output from the FSF GCC, that mostly political detail is highly relevant.
- kevingoslar 12y agoIn my humble opinion most of the success of the open source movement comes from the economics of open source software, and not the licensing. Because unlike physical goods, software can be copied, and thereby given away and kept available to myself at the same time. That creates a situation where sharing software is almost always the better opion than not sharing it (cheaper, easier, faster, stronger etc). If somebody creates a complex non business-critical piece of infrastructure, they have incentive to open source it. Because By doing so they can still use it as before, but get bug fixes and additional features for free from the community. If I create an improvement for that open source code base, I also have an economical incentive to share that improvement back to the maintainers. Because I too can give it away while keeping it. If it gets merged, others maintain it for me, and all future updates to the software already contain my improvement. If I keep that improvement to myself, I have to patch all future versions of the software myself, which becomes harder over time as the software changes. Giving my patches back makes my life easier than not doing it. I'm not against the idea of GPL, and the good intentions it has. It was necessary and good at the time. Some might still seem it necessary for philosophical or spiritual reasons, and that's okay. But most open source software that I'm aware of today, the majority of the open source revolution that the industry is experiencing right now (except for the honorable Linux) seems to be driven more by the economy of software sharing than the contractual requirement to do so.
- UNIXgod 12y agoShouldn't it be "A free letter to RMS" =) I have a feeling Dr. Stallman remembers EGCS, xemacs and much more. What's the old BSD saying "Shut up and hack!" ... amusing s/eliza/M-x doctor/ may also remember the tcl wars also.
- nly 12y agoStallman doesn't care if clouty companies fork GCC and add features he doesn't like. This is a freedom granted to all of us. The point is Stallman himself would rather see upstream GCC become an inferior tool, or fall in to disuse and obscurity, than act in any way which, on balance, would mostly just enable proprietary software. We're talking about a man here who said (just less than two weeks ago at 31C3) that stealing food to survive, given no third option, was more morally justifiable than writing proprietary code for a living. The author of this blog clearly doesn't understand this world view because they've set themselves up with a strawman to knock down, assuming it merely boils down to a strategic error on Stallmans part with regard to what is the most effective means by which to ensure the best products out there are FOSS.
- bilog 12y agoThe problem is that Stallman has painted himself in a corner here. On the one hand, he says: don't use LLVM/Clang, it's dangerous, use GCC instead; on the other hand, he says, no, you cannot add to GCC the features that you would need to use it instead of LLVM/Clang. The net result is that Emacs will not have a set of features that are _essential_ for development of C++ software, which in turn drives people away from using Emacs to other IDEs. He's not furthering the cause of GNU and the FSF, he is not promoting free software, he is _driving people away from it_. What's the point of making all those talks about the importance of free software, if you then actively _prevent_ free software from being useful? Software exist because it has a use, otherwise it's just a worthless exercise in futility.
- slowmovintarget 12y agoIn another thread I criticized Dr. Stallman's responses. I stand by the criticism. _However_, he hasn't actually decided yet, he's just pursuing the matter outside the mailing list. Could we let him either change his mind or reaffirm his initial conclusion as final before we heap extrapolations on to the pile? Should Emacs get complex refactoring and code completion? Yes. Should it get them by way of GCC? Ideally. Will it harm Emacs and GCC if this functionality remains crippled in both components of the tool chain? It seems likely. Has RMS decided to go this way? Not yet. BTW: The latest in the thread is a proposition which RMS actually asked for in his initial response: https://lists.gnu.org/archive/html/emacs-devel/2015-01/msg00223.html https://lists.gnu.org/archive/html/emacs-devel/2015-01/msg00...