4 ms·
As someone who writes AGPL software, I will say to most of us it isn't a downside: I would conceptialize that scenario as "your loss" and hope that my work help
by saurik 10y ago
As someone who writes AGPL software, I will say to most of us it isn't a downside: I would conceptialize that scenario as "your loss" and hope that my work helps give companies who are more friendly to the idea of community software at least a little bit of a competitive advantage over your company. In all seriousness: if you are intending to not contribute changes back (which is the only legitimate reason to avoid GPL variants: because you want to use someone else's work while hoarding your own), your gracious "using" of my software has absolutely no value to me...
- abraae 10y agoTotally agree that it is indeed "our loss". No argument there. I don't want to appear a kook, so I won't relitigate what I said in another reply. But essentially we do want to give back. We just aren't always able to give back everything (at least not right now). AGPL, like GPL, is all or nothing in that way. I don't get the option of giving back something, then giving back more later (OSS is threatening to some people - I have frequent discussion at work re why we give anything at all back). Your software, your rules. You have every right to take this all or nothing position! More power to you. But assuming that anyone that doesn't like AGPL does so because they "want to use someone else's work while hoarding [their] own" is, respectfully, a simplistic and stereotyped point of view.
- brazzledazzle 10y agoI wonder if a modified license that set an explicit fixed boundary would help. "You must contribute back any changes to this software that you make but anything that interacts with it at using its API is exempt from the license." So for example if you took the NFS server source and modified it to be distributed and highly available across multiple servers you'd have to contribute that back but the UI or management software you use build for customer interaction with it wouldn't be "infected".
- shubb 10y agoThe worry, places I've worked, is that the GPL would spread to proprietary stuff, like a kind of legal infection. They worry that if they use an AGPL javascript library for the video player on their front page, they'll have to opensource the whole web application (I've even sat in on debates over weather using GPL3 programs means you have to opensource any source data you use them to process and publish the result). A lot of this is silly, but a lot of it isn't. A large company I worked for stopped using Linux after they were forced by a court to opensource a custom video processing microchip because they ran Linux on the box and drove the chip through a kernel driver.
- brazzledazzle 10y agoThey had to open source the chip design or the driver?
- shubb 10y agoThe chip design. It was a PVR box and an activist group wanted to opensource the DRM system they were using because they knew some important codes were baked into the chip so they took them to court. The court felt that the functionality was shared between the GPL kernel driver and the chip, so the chip fell under GPL.
- shubb 10y agoI haven't been able to find any mention of this online. It was around 2009, and I may have misunderstood what I was being told...