7 ms·
I feel like you're missing the point of the GNU GPL. The original idea behind the FSFs idea of open source was an ecosystem where every new development resulted
by djsumdog 11y ago
I feel like you're missing the point of the GNU GPL. The original idea behind the FSFs idea of open source was an ecosystem where every new development resulted in more open and free code. We're talking about people who truly believed in getting away from commercial software entirely. There were people who felt that one day, Linux desktops could replace Windows and even high end tools like Photoshop and Final Cut would have great open source replacements.
...but that never happened. Apple has tried to remove all GPL code from Mac OS. Where GPL code exists, it's only GPLv2 (like Bash; using an ancient version).
Even though all these companies are embracing opens source, they're embracing only permissive licenses. They're open sourcing the underlying tech stack while keeping all their offerings closed. If you're on Android, you are totally locked into Google services. I've met people who tried only using F-droid and running "open source phones" (minus the drivers of course). Their phones sucked. One of them switched back because she was tired of writing apps to do things she use to be able to do with the Play Store.
The dream of a GPL world where the software is free and you only pay for the hardware, is pretty much gone. We don't have federated systems, and where we do, no one uses them (GNU Social, Miro, Diasporia).
This isn't the open source world some of us envisioned back in the late 90s. I personally, will keep as much of my code under GNU GPL as I can.
- yuhong 11y agoWhat is funny is that Apple is even doing this for code that will never be in iOS, for example Samba.
- caskance 11y agoSome people will never admit they are wrong...
- carapace 11y agoRichard Stallman, however, is correct. (I'm going to get that on a t-shirt, printed in block letters: "Stallman is correct.")
- jordigh 11y agoI would buy a shirt that said "Richard Stallman... was right :-(" with a frownie face and all.
- geofft 11y agoIsn't the argument above that he was wrong? He may have been morally right that free software is an inherent good over proprietary software, but that's sort of a given for this discussion. He was tactically wrong in taking an expansive view of both what free software licenses should enforce and what fell within their realm of enforcement. He was hoping that GCC would be so much better than the competition that people would use it despite it being GPL, and for a long while (e.g., NeXT's Objective-C patches) it was. But the GPL, especially the GPLv3, was perceived as way more onerous than Stallman expected it would be, and eventually it became worth people investing heavily in a competitor just to avoid the GPL. If he had aimed a little less high with the GPL and admitted a plugin architecture / documented IR for GCC earlier, then LLVM may never have taken off. Alternatively, he was tactically wrong in thinking that strong copyleft was required to achieve the goal of software freedom. Note that the clang in the NDK "is now a nearly pure upstream clang," not because they're required to, but because the pace of modern software development makes it genuinely easier to voluntarily submit changes upstream.
- pekk 11y agoIf Apple takes a stance against GPL because they don't perceive it as in their commercial best interest, that doesn't mean Stallman was wrong even in a 'tactical' sense. You can't do anything about haters.
- geofft 11y agoOf course Apple does not perceive the GPL as in their commercial best interest. Back when NeXT was writing what would eventually become Apple's toolchain, Steve Jobs tried to convince Stallman that he could come up with a plugin architecture and keep the Objective-C bit private. Stallman went to his lawyer and came back and said, no, you can't do that. Steve Jobs' perception, and NeXT/Apple's perception, never changed. What changed is that in the NeXT days, GCC was so much better that Apple said, we'll make the tradeoff of using GCC even though we don't want the GPL. A few years ago Apple said, we'll make the tradeoff of avoiding the GPL even though we want GCC. And they went and invested significant resources into LLVM. The GPL was meant to be a tool to get people who did not perceive free software as in their best interest to contribute to free software anyway. It might not have changed whether they were "haters" as a matter of opinion, but it was definitely intended to change their concrete actions. And it did -- for a very long time.
- JoshTriplett 11y ago> I feel like you're missing the point of the GNU GPL. The original idea behind the FSFs idea of open source was an ecosystem where every new development resulted in more open and free code. First of all, "FSF's idea of open source"? They'd rather vigorously object to that phrasing. :) But no, that was exactly my point: I'd argue that intentionally choosing to not allow the development of a library version of GCC, even under the GPL, caused a net reduction in the amount of Free Software in general, and copyleft-licensed Free Software in particular, that would otherwise have been developed.
- dragonwriter 11y agoRMS -- and perhaps the FSF more generally -- seems more concerned with preventing non-Free software, with creating Free Software as a means to that end, than increasing the volume of Free Software. To RMS, non-Free software isn't just worse than Free software, its a net harm to society such that it's better to have no software than to have non-Free software. Its even often (apparently, to RMS) better to have no additional software than to have a lot of additional Free Software and some additional non-Free software.
- rimantas 11y agoSo FSF is basically PETA of software world.
- anilgulecha 11y agoNot really.
- JoshTriplett 11y agoI wouldn't describe the FSF's position that way (they value Free Software for its own sake, and their goal is that all software should be Free Software), but even if that were their position, I'm arguing that their handling of GCC and refusal to support it as a library directly motivated the creation of LLVM and led to a scenario that better supports the creation of proprietary software. Providing a GCC library would have significantly lessened the motivation for LLVM: many of the "we need a library" folks would have one, leaving just the "we need a permissively-licensed library" folks, and the "GCC's codebase is awful" folks. (And even some of the latter group might have worked to fix GCC.) That's not the only thing done wrong with GCC development. The much worse problem is that GCC doesn't really support reviewing and accepting patches; you pretty much have to have commit access to do any significant work on GCC.
- micampe 11y ago> The dream of a GPL world where the software is free and you only pay for the hardware, is pretty much gone. I feel like you are missing the point of the GNU GPL.
- malka 11y agoyeah. Software can be both libre and not free (as in you have to pay for it). The only difference being that once you paid for it, you OWN it, the same as you own, say your shoes (I was going to go for the car example, but that is less and less true. We do not own our car anymore.)
- dozzie 11y agoThen a bicycle perhaps.
- stcredzero 11y agoThe original idea behind the FSFs idea of open source was an ecosystem where every new development resulted in more open and free code. So let's put it this way: The FSF didn't pivot when they had a chance to capture a larger market!
- anonbanker 11y agoonly on hacker news would someone spell "pivot", but pronounce it "sell out". I'll bask in the downvotes that comes with telling the harsh truth. I got karma to burn, folks.
- stcredzero 11y agoNo, not "sell out." Pivot. They could have served their users even better, but they didn't out of stubbornness. Now the market has spoken.
- anonbanker 11y agoWhen "pivot" means "compromise your internal values to be profitable", you have sold out, my friend.
- skybrian 11y agoIt's unreasonable to expect commercial software companies to do all the work to build a free software ecosystem, since that's not what they're about. Still, they've made some substantial contributions. F-droid might not be good enough yet, but they're still a lot further along than they would be starting from scratch, without Android. So although it hasn't succeeded for phones yet, building on top of tech stacks contributed by others (who haven't fully bought in to the same goals, but are sympathetic in some ways) still seems like a great strategy. The free software community needs to finish the job. On the other hand, going fully independent and building stuff separately without those contributions (which seems to be what some free software folks want to do with commercial-unfriendly licenses) doesn't make a whole lot of sense to me. If you can't succeed even with substantial help, how do you succeed without help?
- hjek 11y agoi'm not the big android user, but having used cyanogenmod with fdroid and free apps exclusively for a bit, i'm quite impressed with the free software userland, especially offline maps and puredata-patch runner, pddroidparty. pity about the drivers though. at a speech in copenhagen stallman was encouraging people to start reverse engineer these. it's nice that at least some of the phones are somehow open.
- dragonwriter 11y agoThe web itself is a federated system, running largely on Free software, built to open specifications. (Email, too.) The idea that we don't have federated systems and that those that do exist are unused isn't particularly based in reality. It's true that the Free Software federated systems that are more strongly based in ideology that bringing use-value to users have generally failed to experience uptake, but that should probably not be considered a surprise.
- bonzini 11y agoWhile it's running largely _on_ free software, it's running largely non-free Javascript on the end user machines which are those that matter.