I fully support open source software, but it’s not feasible under the current economic system to expect everyone to exclusively contribute to open source projects.
You’re allowed, but as long as anyone else can do it for free, you can’t build a business model on selling it. At most you can sell something else (support, cloud compute, some solution that makes using it easier etc.).
Which means in the long run the cost will get down to 0.
The moment the code and redistribution rights are out in the open, anyone who tries to charge for it faces competition from people charging less — and eventually from people charging nothing. The economic pressure pushes the price down to the cost of copying, which in the digital world is effectively zero.
Technically, according to the GPLv3 you don’t need to make the source code publically available. If you sell software with binaries then their source code must be included with it. If you’re Red Hat you can also add an additional ToS to the website that states if you buy the software you can’t freely distribute the source code you download from the website or you will be sued to oblivion.
No, they don’t say they will sue (they flat out can’t), but they say they will cut off your access to any updates.
Now one could (and I would) argue that sounds like a restriction on exercising your open source rights. However the counter argument seems to be those protections apply only to software acquired to date, and if you deny access to future binaries you can deny access to those sources.
In any event, all this subtlety around the licensing aside, it’s just a bigger hassle to use RedHat versus pretty much any other distribution, precisely because they kind of want IBM/Oracle style entitlement management where the user gets to have to do all the management work to look after their suppliers business needs.
You must make the source available to anyone you distributed the binaries to. Where in Red Hats TOS does it say they will sue you? As far as I understand it the reserve the right to terminate the service you are paying for. But your rights to source for the binaries provided are not affected.
Sure, and I recognize that it’s not a great metaphor. But I’m thinking about it from the developer side. Open Source software is not motivated by profits, and profit motivates a lot of developers. Some of the best software projects were actualized by a few committed individuals who were passionate about the purpose. But then you have Microsoft which tries to tie bonuses to lines of code, and ends up with bloated garbage because peoples is peoples.
Open source is good, in the same way free lunches for school children are good. The benefits are innumerable. But it’s not feasible to expect every developer to commit to open source projects when their efforts might not be rewarded.
Aren’t “consume” and “support” different concepts? The article is trash, so I’m not referring to that, but I could take this stance in broader terms.
My voluntary time and money is limited, so if you keep your work proprietary, I’m not going to provide it to you any more than I absolutely need to in a basic, transactional sense.
If my boss says work on this project -I’ll do it because I’m paid to do that, for the amount of time I’m paid to do it, but no more. If my bank says use this closed source application, okay fine, but I’ll never recommend it to anyone or submit a bug report when it breaks. If my government or library is considering entering into some closed source ecosystem, I’ll go out of my way to recommend against it, but I’ll probably end up having to use it. If I feel like paying for Netflix, I’ll share passwords and use regional VPNs, cancel whenever I feel like it, or whatever and never feel guilty.
If your product is open source, pretty much the opposite of all of the above. That’s what I would consider as “support.”
“I only eat food that’s free.”
I fully support open source software, but it’s not feasible under the current economic system to expect everyone to exclusively contribute to open source projects.
You are allowed to charge money for open source.
Its the recipe that makes the food you’re eating that would need to be publicly available and free to redistribute.
Removed by mod
many governments are currently trying to tear down art grants aren’t they tho?
the majority keep voting for the people trying to break everything and get shocked when it breaks.
You’re allowed, but as long as anyone else can do it for free, you can’t build a business model on selling it. At most you can sell something else (support, cloud compute, some solution that makes using it easier etc.).
I don’t know why you’re getting downvoted. What you said is true.
It reminded me of an older writing about it:
Open source doesn’t make money because it isn’t designed to make money
Canonical seems to make some decent money off of their services.
You can build a business model on selling it, but you can’t stop someone else doing the same.
Which means in the long run the cost will get down to 0.
The moment the code and redistribution rights are out in the open, anyone who tries to charge for it faces competition from people charging less — and eventually from people charging nothing. The economic pressure pushes the price down to the cost of copying, which in the digital world is effectively zero.
Technically, according to the GPLv3 you don’t need to make the source code publically available. If you sell software with binaries then their source code must be included with it. If you’re Red Hat you can also add an additional ToS to the website that states if you buy the software you can’t freely distribute the source code you download from the website or you will be sued to oblivion.
You cannot make restrictions to the distribution of the source code under the GPL
No, they don’t say they will sue (they flat out can’t), but they say they will cut off your access to any updates.
Now one could (and I would) argue that sounds like a restriction on exercising your open source rights. However the counter argument seems to be those protections apply only to software acquired to date, and if you deny access to future binaries you can deny access to those sources.
In any event, all this subtlety around the licensing aside, it’s just a bigger hassle to use RedHat versus pretty much any other distribution, precisely because they kind of want IBM/Oracle style entitlement management where the user gets to have to do all the management work to look after their suppliers business needs.
You must make the source available to anyone you distributed the binaries to. Where in Red Hats TOS does it say they will sue you? As far as I understand it the reserve the right to terminate the service you are paying for. But your rights to source for the binaries provided are not affected.
It’s not a perfect metaphor.
None are.
I don’t mind paying for software.
I want free as in freedom, not free as in beer. Though a free beer might not be the worst thing in the world
Sure, and I recognize that it’s not a great metaphor. But I’m thinking about it from the developer side. Open Source software is not motivated by profits, and profit motivates a lot of developers. Some of the best software projects were actualized by a few committed individuals who were passionate about the purpose. But then you have Microsoft which tries to tie bonuses to lines of code, and ends up with bloated garbage because peoples is peoples.
Open source is good, in the same way free lunches for school children are good. The benefits are innumerable. But it’s not feasible to expect every developer to commit to open source projects when their efforts might not be rewarded.
Aren’t “consume” and “support” different concepts? The article is trash, so I’m not referring to that, but I could take this stance in broader terms.
If my boss says work on this project -I’ll do it because I’m paid to do that, for the amount of time I’m paid to do it, but no more. If my bank says use this closed source application, okay fine, but I’ll never recommend it to anyone or submit a bug report when it breaks. If my government or library is considering entering into some closed source ecosystem, I’ll go out of my way to recommend against it, but I’ll probably end up having to use it. If I feel like paying for Netflix, I’ll share passwords and use regional VPNs, cancel whenever I feel like it, or whatever and never feel guilty.
If your product is open source, pretty much the opposite of all of the above. That’s what I would consider as “support.”