4 ms·
While I'm in favor of this, it makes me question somewhat the potential unintended consequences of something like this, in that it makes shipping actual hardwar
by hn_throwaway_99 5y ago
While I'm in favor of this, it makes me question somewhat the potential unintended consequences of something like this, in that it makes shipping actual hardware devices with actual software on the device even less appealing.
That is, if I provide a SaaS platform, my understanding is that even if I use all types of GPL code to run my service, as long as I don't "ship" the code for that service to end users (which is like 99% of all SaaS products when it comes to backend services), I don't need to share my code.
But if I release a hardware product and by definition I need to ship that code to end-users, then I do need to share my code. Just seems to be an incentive to make more and more stuff "subscription based" with a backend service. Though, due to other economic incentives businesses want to do that anyway, so perhaps my point is moot.
- spijdar 5y agoI think the response of advocates would be that the solution is for more people to use AGPL, which would fix that "loophole". Now, I don't see AGPL becoming widespread personally, but this is essentially its reason for existing.
- bluGill 5y agoIt just drives more companies to be more careful about their license. My company has for years banned any GPL3 code on devices we ship. If GPL2 is suddenly found more restrictive than we expected we will ban that too. FreeBSD/NetBSD will be the winner there, along with other projects. We don't contribute much, but we already consider license before we contribute back - and if we can't get GPL code we will make the changes needed to BSD code. Most of our changes will be contributed back - only changes that are actually things that matter to us will be withheld and those are not part of open source projects to anyway)
- Seirdy 5y agoThe point of copyleft licenses is to make it hard to make proprietary software and easy to make free software. It sounds like they're working as intended. My understanding is that this suit is partly on the grounds of Visio not releasing modifications to copylefted code. The MPL and LGPL have the same requirements; is not being able to use LGPL, GPL, AGPL, MPL, or CeCILL-licensed software really harder than compliance? Stories like this just make me all the more convinced that the right approach is to make software a commoditized complement of a service; software is not as scarce a resource as labor.
- bluGill 5y agoA large amount of free software is developed by companies. If they stop it hurts us all.
- Seirdy 5y agoLike I said, companies are free to use a more sustainable model that doesn't require artificial scarcity: they can provide services to reflect the fact that copies of software are not a scarce resource, while labor is. It's not our duty to keep old business models alive. We shouldn't try to appease companies so they do what we like; they're the ones who should adapt to our needs.
- drewg123 5y agoYes, exactly. This is how companies react.
- chii 5y agothat's why i am a huge fan of the AGPL - prevents this from happening. If you leverage your product with open source, there must be some sort of contribution back - either you pay the creators of the open source with a license fee, or re-contribute your own efforts via source code release. there shouldn't be free lunches.