That this is connected to how "valuable" code is, is in a sense a happy coincidence. The conditions are attached and entangled because this forces people to listen and pay attention.
A more "permissive" license (like BSD) is weakening that point. It allows you to reuse code but does not require the re-user to allow the above mentioned openness. So is kind of missing the point, from that perspective.
That is the dogma, but in practice it is false. Khtml was GPL, that didn't stop Apple from forking it in such a way that their changes couldn't be reused. In practice many who change BSD software find it worth while to contribute their changes back - so they can continue to use the latest version instead of maintaining their own fork.
> There is some value to having windows itself, but the more valuable thing is the horde of programmers, and all the other resources behind it.
This is partly true. What's valuable is for code to do things for people. For that to happen, you need programmers who can make that code, and maintain it over time. The way companies make money on proprietary software is by controlling the intersection - they control the access to code and programmers who can work on it, so if you, as end user, want your computer to do something, you have to pay them. If you want the program to do something else, you have to pay them (or their partners, friends, subsidiaries) to make the modifications/extensions.
GPL exists to defeat this stranglehold. It does it in two ways. First, like permissive licenses, it ensures you can modify the code yourself, or commission some programmers to do that for you. Secondly, unlike permissive licenses, it ensures that you can't just turn around and lock down your improvements, preventing other end-users from doing to the improved version the same thing you just did to the base version. In this way, it ensures the money can only flow from users requesting work to programmers doing the work - it removes the ability to seek rent for the work already done. It removes control over users from the hands of companies and software developers.
Permissive licenses are obviously preferred by software industry, because they give more control to us, software developers, at the expense of end users.
Maybe the license isn't the correct place to address this. I'm not sure what the solution is, though...
I really liked that comparison and I've thought about it a lot since. And here it's worth asking, how did we go from alchemy to science? How did we end up figuring out that openness and transparency is beneficial?
I know one thing, it wasn't with licenses. But I'm really curious, because I want to live in the world where open source is the default. I just don't know how we get there.
Licenses only matter because there's trademarks and copyright. In places where IP isn't protected as much, they also would not matter, in a way that they would not be necessary. But because stuff can be copyrighted, there also must be a way to share that, aside from liberating it from the copyright of course.
I think a close real-life analogue is a potluck. The custom requires that participants bring some food, and in turn can consume from what the others brought. And it's a nice old thing too, with etymology dating back to the 16th century.
Removing patents and copyright from public funded universities is an on-going struggle that has yet to be fixed. We have yet to start to make all scientific research free from patents and copyright.
We should strive towards the utopia where all that was expected is that people will cite the source, and then everyone could build off the work of everyone else.
Research is not copyrighted. Particular write-ups of the research are copyrighted.
That paper would be subject to copyright.
However, if I go read the paper at the library and then use the knowledge I gained from it to make the superconductor and test it and applied the theory I learned from the paper to other superconductors, that would not violate the copyright of the paper.
If I wanted to then tell you how to make the superconductor, I would not be able to make a copy of the original paper and give you that copy. That would be violating the copyright on the paper.
But I could write up my own description of how to make it in my own words, using what I learned from the paper, and give you that description. That would be fine from a copyright point of view.
The GPL doesn't give primacy to the thing that's built - but to the user of the thing. The GPL implicitly values the user's freedom over developer's convenience - the opposite is true for BSD-like licenses.
Generally, I feel like the affinity most people have to one license or another entirely depends on how they more closely identify as a user of. software, vs as a developer
That assumes a very specific kind of user. The kind that has the time and energy, not to mention the ability, to read and understand source code and modify it according to his needs. Basically the RMS kind of user.
For most users, that freedom is not much of a concern at all. For them, the most important freedom is: the freedom to enjoy the fruits of labour of a large horde of programmers who can make a fruitful living out of creating apps for said users.
They enjoy this freedom a lot more in what GNU calls non-free platforms like Windows and Mac and iPhone, which is why they keep flocking to them.
Actually, no. End users also benefit when code is contributed back to the software they use.
My intent was only to help the GPL and free software fanatics see an important freedom provided by non-free platforms, not to belittle the achievements of open source community.
Saying that the source availability is not important because you won't use it is like saying free speech is not important because you have nothing to say.
Anyway, like I have already said, my intent here was only to try to make people like you see another perspective (namely that non-free platforms can create ecosystems where users enjoy the labours of a large number of developers who can make a profitable living out of programming for that ecosystem - access to such ecosystems is also a freedom and one that many users care about). Apart from making that limited point, I had no interest in having a pointless argument with an open source fanatic.
Apart from that, It is clear from my comment history that I do have a side. Nevertheless, calling me an "open source fanatic" is kind of rude.
Sounds a bit like "I don't care about free speech, I don't want to say anything!".
Looks like you got too excited to be able to read the entire comment? XD
> it is like saying free speech is not important because you have nothing to say
The only thing your "alternative" reply changes from that is grammar.
As for scientific research, most of the software behind scientific paper is basically closed source. Which is another reason why there's a whole reproducibility problem with science papers: it's quite possible many papers are just bad interpretation of data due to bad software.
Also note how much software / research / data is proprietary. How can one quote that?
I wouldn't mind using only BSD in the future if I get to read the Apple iOS source code on GitHub.
Even copyright... isn't Elsevier a major copyright holder for all academic papers and thus causing all sorts of problems. It's not like it's all kumbaya out there. The academic world is much worse than GPL and open source on multiple dimensions.
I suppose the academic world might be considered worse than GPL in some copyright sense, but not in the practical sense of sharing/reproducing/extending results. And, of course, one does not need to publish with Elsevier -- there is no shortage of "open-access" journals.
No, I could be wrong, but it’s my understanding that the author of the academic paper still holds the copyright, it’s just the author licensed sole (or near exclusive) distribution rights to Elsevier in exchange for publication in their journals. It’s basically the same in the publishing world, I own the copyright on the book I coauthored, but WROX Press owns the distribution rights as we gave those up in exchange for them publishing.
2) Yep, the whole idea of GPL is to allow those good sources to propagate freely and get reused. Read the license, please.
3) Citation model is the core of BSD license, so use it for your own code.
I see a lot of value in not pointlessly reinventing the wheel. GPL encourages/enforces people who fix things to give those changes back to upstream where they may benefit everyone. So ideally only one set of fixes per problem has to be globally implemented and maintained.
The implications for global wealth are non-trivial. How much Linux alone has done, I wonder?
One can argue GPL encourages reinventing the wheel by not being permissive enough.
Microsoft Copilot uses billions and billions of lines of code. It charges for the service. If Microsoft had to license the code, could it build as good a service? If not, then that proves that the (trillions of) snippets have value. Microsoft only says it's valueless because it can get away with stealing it.
It's the same way water is free at the river. But that doesn't mean it has no value. Water has price tags in a supermarket.
When Google photographs billions of streets it at least provides a public service with it and a way to remove yourself.
Centuries ago, petrol was considered useless and a nuisance. Now it's very valuable because it has uses. Microsoft is trying to convince people that petrol has no value exactly because it does.
Just because every line of code is worth millionths of a penny, doesn't mean it's valueless when Microsoft will make billions of dollars off of the service.
Because people don't hide their equations and ask you to pay them money to evaluate them given a set of variables.
GPL wouldn't be necessary if sharing code were already the default. It's an ugly hack to solve a really stupid artificial problem.
The human element of the programmer who can understand, adapt and develop some program is more valuable. The valuable thing is their time and overall knowledge, not the end piece of content necessarily. I think you do want to make sure people who have good ideas get recognised, (but this is like GitHub, employment record etc) but truly it's more beneficial to society if those good ideas propagate freely and get reused. I think the copilot thing really brings this to light. I believe BSD is probably the best option.
Valuing the programmer more, caring more about who develops your app is more important than merely the code at the end of the day. Eg is this a reputable team I want to support? The copyright/license system seems out dated in light of new information. I think the citation model works better. If its truly well established knowledge then yes maybe a formal reference exists somewhere, but they sort of fade into the background.