6 ms·
> the GPLv3 was simply far too scary for companies. The FSF made a huge effort to make GPLv3 not scary. They tried to involve absolutely everyone, and tried t
by teddyh 6y ago
> the GPLv3 was simply far too scary for companies.
The FSF made a huge effort to make GPLv3 not scary. They tried to involve absolutely everyone, and tried to take everyone’s concern into account. The GPLv3 was made to be not scary.
The GPLv3 instead became “scary” not because anything scary in it, but because of a huge FUD campaign from large companies who didn’t want people to switch from GPLv2 to GPLv3, since the companies wanted to keep exploiting the loopholes in the old v2. For those old enough to remember, this was mostly the same old FUD campaign against the GPL (any GPL) versus a permissive license, many years before that. But, largely thanks to Linux, the GPL slowly won over that old batch of FUD. With the GPLv3, however, the opportunity was there to start it all up again. The GPLv3 is slowly winning against the FUD this time too, but it hasn’t prevailed yet, and Linux is not here to help this time.
- sneak 6y agoNot everyone agrees that the freedom to start a SaaS business with GPL software is a "loophole".
- hnarn 6y agoI wonder when this idea really started propagating, was it around when AWS came along? Because by a technical definition I don’t understand why this “loophole” wouldn’t also apply to a hypothetical web host back in the late 90s.
- rakoo 6y agoThe GPL has no element saying it can't be used to start any kind of business, and I don't think any of its defenders has ever said the GPL's goal is to suppress that freedom. It seems the FUD is still going strong.
- sneak 6y agoThe same people who made the GPL use the term "ASP loophole" and made the AGPL. Not everyone agrees that the freedom to make a SaaS business with a private GPL fork is a loophole or bug. It seems (from their creation of the AGPL and use of terms like "ASP loophole") that the GPL people do.
- posguy 6y agoNot everyone has trouble with AGPLv3 being the core of their SaaS business. Just because your core business software is AGPLv3 doesn't mean any other business will be able to build a coherent business model atop it, look at Kazoo by 2600Hz or Iris by Lowes. Knowing how to properly configure and maintain said code in production, creating integrations with third party vendors (that your competition likely can't interact with on the same terms) and marketing to build mindshare among potential customers is a common way to offer your core software as AGPLv3 yet have no competitors or few competitors use your core software.
- Dylan16807 6y agoBut the comment you replied to was about the v2->v3 loophole fixing. That has nothing to do with AGPL, it's about bootloader locking.
- kmeisthax 6y agoAGPL isn't pro- or anti-SaaS, though. It just says that you have to provide sources to anyone you grant access to the software over a network. So if you host an AGPL database for someone else, they need access to the source code for that database somehow. But it doesn't prohibit you from hosting the database at all. It's the perfect license for MongoDB and all these other companies trying to keep Amazon from taking their software and proprietarizing it... but instead they make weirdly restrictive one-off licenses nobody are going to contribute to.
- sneak 6y agoAGPL restricts developer freedom simply because they launched a webserver on the same machine. There is a legitimate logical argument that the AGPL is not free software.
- Iolaum 6y agoThe whole idea behind copyleft, hence free software as Stalman envisioned it, is to restrict the developer's freedom in favour of the user freedom.
- chimeracoder 6y ago> Not everyone agrees that the freedom to start a SaaS business with GPL software is a "loophole". Neither GPLv3 nor GPLv2 prohibit this. You're thinking of the AGPL, the first version of which was based on the GPLv2 and released in 2002, years before the FSF announced that they were even beginning work on the GPLv3.
- cma 6y agoThe reason people confuse it is because early work on GPLv3 was going to include similar clauses but they were later abandoned.
- kazagistar 6y agoThats wrong too. If you use an unmodified version of AGPL software, or just host any modifications in a public repository like github, then you aren't in violation of AGPL, even if the rest of your stack is proprietary and your service paid. How does it prevent SaaS?
- ckocagil 6y agoAre you thinking of AGPL instead of GPLv3?
- rakoo 6y agoAGPL, like any version of GPL (and most if not all open source licenses) does not prohibit anyone from starting a business. It's weird this FUD is still spreading after all this time, after all the debates the community has had already. AGPL does have restrictions, and it's anyone's preference as to whether they're good or bad, but there has never been an intent to forbid businesses. If anything it's the recent RedisLabs' modules license and the SSPL-style licences that do it: they explicitely contains the wording to indicate that the product can't be used to create a similar product and offer it as a service. Heck, the SSPL says (https://www.mongodb.com/licensing/server-side-public-license https://www.mongodb.com/licensing/server-side-public-license): "If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge, under the terms of this License" The AGPL tells you that if a user asks for the source code, you must give it to them and them only. The SSPL says that the source code must be publicly available to all, at no cost. It was created specifically to prevent competitors to run MongoDB as a Service. Surely if they had to change it's because the previous license did authorize competitors to do it. Wanna take a guess what the previous license was ?
- xyzzy_plugh 6y agoI can count the number of remotely successful businesses built on AGPL software on one hand. The AGPL doesn't prohibit starting a business, it makes starting a business prohibitive.
- posguy 6y agoOwnCloud, NextCloud, Linphone (their pricelist starts in the 5 figures for support!), etc all run successful businesses off AGPLv3 code. Amazon is notorious for turning AGPLv3 projects and products into SaaS services! Look at all the SaaS offerings of MongoDB (formerly AGPLv3): https://news.ycombinator.com/item?id=19362919 https://news.ycombinator.com/item?id=19362919 AGPLv3 doesn't make starting a business prohibitive, arguably forks like NextCloud would not exist if AGPLv3 did not compel codebase users to publish the additional code they wrote to extend OwnCloud
- bosswipe 6y agoAlso I think GCC's loss of prominence due to LLVM hurts the pull of the whole GPL ecosystem.
- xyzzy_plugh 6y agoIsn't this the other way around? LLVM makes it easy to embed parts of the project into IDEs, linters, etc. My understanding was that Stallman continually fought to keep GCC difficult to avoid linking with if you wanted to use parts of it. As I see it, once LLVM became competitive with GCC, adoption quickly accelerated due to liberal licensing.
- girvo 6y agoMaybe I’m misunderstanding but it seems you’re totally in agreement!
- xenadu02 6y agoIf by "involve everyone" you mean "ignore the many many companies that said the current GPLv3 is a non-starter and will entirely end our involvement" then sure. They decided to pick an ideological bone on purpose. That's fine, it's their right. But it was a deliberate decision knowing the consequences.
- gcblkjaidfj 6y agoFSF picked the bone that needed to be picked. Well, they should have addressed tainted linux kernel firsts... but oh well. It is ironic (and sad) how people here campaigning against GPLv3 are all happy and warm when they realize they can download the driver and kernel sources for their modem, phone, rPI or whatever device. But then if someone want to even suggest the same thing for digital products, then, no, it's the end of the world.
- jancsika 6y ago> The FSF made a huge effort to make GPLv3 not scary. If they were serious about that effort, the metric would have been a simple boolean: "Will the Linux kernel make the switch?" That's got to be your most visible, most well-funded GPLv2 project in existence. If no (and it was a resounding no according to Linus' very public rant at a Debconf a few years back) then the license would almost by definition appear to be "scary" from the outset. The only exception would be some very rare edge case in Linux that makes it impossible to switch. In reality-- again, at least according to Linus-- it was a complete breakdown in trust between a holder of the old license and the organization writing the new one. I don't know the intricate details, but it's clearly a bigger problem than "large companies" spreading FUD. Edit: clarification
- ndesaulniers 6y ago> it was a resounding no according to Linus' very public rant at a Debconf a few years back This one? https://www.youtube.com/watch?v=PaKIZ7gJlRU&t=241 https://www.youtube.com/watch?v=PaKIZ7gJlRU&t=241
- jancsika 6y agoYes, thanks for the link. Digression-- I'm sure the FSF doesn't appreciate it, but there is something very disarming about Linus ending his rant calling the entire FSF "bigoted people," and then immediately following it with, "I may have overstated that a bit." It's a very unprofessional and risky way to joke around, especially after making the accusations he made minutes before. But the fact that you can hear how the room laughs and carries on after he essentially calls himself a "drama queen" tells you that pretty much everyone understood the upshot (whether or not they appreciated the joke). That makes me think that of how rotten online communication is. In person, a maintainer of one of the biggest open source projects can call an entire organization one of the worst insults, and probably none of the members of that organization in attendance even considered interrupting him. Yet HN needs a "cool down" period to keep participants arguing about semicolons from throwing their device at the wall. Edit: typo
- sam_bristow 6y ago