3 ms·
Under GPLv2, you can use the code base you contribute to how you desire. With GPLv3 there are additional restrictions on how you can use the code base you cont
by slownews45 5y ago
Under GPLv2, you can use the code base you contribute to how you desire.
With GPLv3 there are additional restrictions on how you can use the code base you contribute to.
- yjftsjthsd-h 5y agoOkay, I desire to run the software on the hardware that I literally bought to run it.
- _ph_ 5y agoAs do I. As a customer buying some hardware, I would of course like to have access to the software stack as well. And be it only for long-term support after the device becomes unsupported. But for various reasons, a lot of companies (and it is usually the decision by the company, not the employed developer) selling the products, don't want to give you this ability. Sometimes it is for making more money, sometimes it is for legal and safety reasons, just think of the automotive sector. If a company decides to sell you a product with closed software, they will do so and GPLv3 won't change this. Not because they are not complying with the license terms, but because they won't touch any GPLv3 licensed software.
- slownews45 5y agoThe point I'm making is that DEVELOPERS pick the license, and formerly for them they didn't lose much of their freedom by picking GPLv2, just others could also take code and do things. With GPLv3 that changed. Others could still take code and do things, but now they COULDN'T do things. Users desire is not part of this, and is a boring and old trope of OSS where users, doing no work and paying no money - make all sorts of demands. If that is the FSF attitude then good riddance to them, it's old and burns everyone out. They probably have attorneys going crazy and burning out people even more.