4 ms·
That’s so sad. I’d hate to work at a shop that wouldn’t allow AGPL’d software for internal tooling. What a completely legally unnecessary, productivity-hobbling
by kstrauser 3y ago
That’s so sad. I’d hate to work at a shop that wouldn’t allow AGPL’d software for internal tooling. What a completely legally unnecessary, productivity-hobbling decision.
Perhaps the best feature of the AGPL is that it predominately hampers companies with ineffective legal departments.
- _atreeonmyhouse 3y agoOne of the most notable examples is Google.
- kstrauser 3y agoPity. They said it’s because they’re afraid someone outside Google would use it, which is legitimate for companies without sufficient technical SBOL controls to prevent using third party software in violation of its terms. Their take is basically “we don’t have a way to keep our internal software internal, so you can’t use it at all, ever, for anything”. I wouldn’t have expected that of them.
- hedora 3y agoThat makes sense. GPL 3 is basically a non-starter for people that ship hardware, but is fine for people that provide web services. AGPL would level the playing field between Google and device manufacturers and on-prem software companies (like Apple and Microsoft). Of course they don’t want their employees to use and indirectly support that ecosystem! I wish they’d produce a GPL 4 that is closer to the AGPL. v3 backfired and is severely hurting end-users’ freedom in practice.
- GuB-42 3y agoI know, but why? Due to their size, they must have one of the best legal department in the world. Also, their core business is search, and data processing in general. They have the means of using such software and doing what it takes to comply with the licence without putting themselves in trouble. My guess is simply that they don't want to. They prefer to rewrite it, which will allow them to monetize their tools as proprietary software later. They are already overstaffed with some of the best developers, they can rewrite stuff, and they don't really need help from the open source community, that's why they don't release under copyleft themselves.
- DangitBobby 3y agoLicenses intended to be viral and poisonous are avoided by companies interested in ownership over their own IP. Huge shocker.
- josephcsible 3y agoWhat do you mean by "poisonous"?
- fungiblecog 3y agoIt's just a classic F.U.D (fear, uncertainty and doubt) tactic
- deleted 3y ago[deleted]
- DangitBobby 3y agoThey are intentionally dangerous to unwitting license holders who wield them wrong.
- nine_k 3y agoI suppose it's about the patent clause.
- komali2 3y ago> viral and poisonous Viral, perhaps if you integrate a library, but in this case it doesn't make sense, you only need to distribute source code if you modify it. Poisonous makes no sense to me, can you clarify? https://www.merriam-webster.com/dictionary/poisonous https://www.merriam-webster.com/dictionary/poisonous 1. DESTRUCTIVE, HARMFUL ... 3. SPITEFUL, MALICIOUS In what ways is the GPL or AGPL destructive or harmful or spiteful or malicious? I find it the exact opposite of all those concepts.
- kstrauser 3y agoIt’s not, except to people who want to use GPLed software without holding up their end of the bargain.