No they really wouldn't. Companies and fans would commission art. We pay our damn food service staff on “would you like to pay a little extra today” tips method. Don’t tell me, especially with zero justification, that creatives depend on the need to control who copies our society’s ultimately culture. There are absolutely other ways and we’re too scared to try them.
They don’t have a right to extract art from artists… commission means pay for a piece up front, not after the fact. And on top of that you can only make digital copies cheaply.
Again they would not be “stillborn”. We’ve figured out crowdsourcing and popularity-based compensation (YT, patreon, etc.). You are just making statements without backing them up with readonable arguments.
The person you're replying to explicitly stated that a different way to compensate creatives for their talents should be put in place in case copyright is eliminated.
We already have systems that work better. None of them depend on copyright. Crowdfunding [generally commissions], patreon-type platforms, sponsored content, live performances, etc etc etc.
Every bit of open source is founded on the license enforced by copyright and the ability for the creator to authorize the creation and distribution of derivative works.
Without it, anything that is published could be taken (once the copyright has expired), repackaged in some user inaccessible way and resold.
It is copyright that enforces the license of GPL. Without copyright, no license on creative work has any teeth.
The GPL is considered by its author to be a “hack” on the copyright system to perpetually enforce source availability. Most consider it unnecessarily restrictive and would prefer a world without it, Stallman included. But since Xerox used copyright to sue people trying to fix their own broken copiers, which they owned, here we are.
Point is, removing copyright also removes the need for the GPL in the first place. All knowledge should be public ___domain.
Removing copyright allows a company to take something that is in the public ___domain, make changes to it and not release the changes.
Yes, the GPL is a hack on the distribution of derivative works... but without those teeth to bite with and enforce, then nothing prevents one from taking some code that is not-copyrighted, making changes to it, and keeping the code to it completely in house while releasing it in a way that is not user modifiable.
The ideals of the GPL (and AGPL) of sharing the contributions back to the community to further progress would be unenforceable and lost.
You forget that because the company cannot enforce copyright, I can just take whatever bits the company distributes to me and do what I please with them. I wouldn’t he opposed to a broad law requiring software companies to make buildable sources available for all software they use to deliver a product, but I doubt we’re that liberal yet. That is essentially what Stallman was asking for and the GPL is a means.
If I took iText, made changes to it, rebundled that behind a web service - that would be in violation of the AGPL. The thing that prevents that from happening is that the AGPL prevents it based on copyright.
It would be unreasonable to say that every web site out there or SaaS service needs to provide the source code to rebuild their site by someone else.
I will also point out the "write a law" would only apply to one country. Host it in another country and you could thumb your nose at the law. You would really want an international treaty such as the Berne Convention, or TRIPS, or WCT... which are implemented as copyright. Any changes to copyright would imply that that country is withdrawing from those treaties.
And we just had to suffer with waiting. It would take an hour or two to
get your printout because the machine would be jammed most of the time.
And only once in a while -- you'd wait an hour figuring "I know it's
going to be jammed. I'll wait an hour and go collect my printout," and
then you'd see that it had been jammed the whole time, and in fact,
nobody else had fixed it. So you'd fix it and you'd go wait another
half hour. Then, you'd come back, and you'd see it jammed again -- before
it got to your output. It would print three minutes and be jammed
thirty minutes. Frustration up the whazzoo. But the thing that made it
worse was knowing that we could have fixed it, but somebody else, for his
own selfishness, was blocking us, obstructing us from improving the software.
So, of course, we felt some resentment.
And then I heard that somebody at Carnegie Mellon University had a copy
of that software. So I was visiting there later, so I went to his
office and I said, "Hi, I'm from MIT. Could I have a copy of the printer
source code?" And he said "No, I promised not to give you a
copy." [Laughter] I was stunned. I was so -- I was angry, and I had no
idea how I could do justice to it. All I could think of was to turn
around on my heel and walk out of his room. Maybe I slammed the door.
[Laughter] And I thought about it later on, because I realized that I was
seeing not just an isolated jerk, but a social phenomenon that was
important and affected a lot of people.
Now, this was my first, direct encounter with a non-disclosure agreement,
and it taught me an important lesson -- a lesson that's important because
most programmers never learn it. You see, this was my first encounter
with a non-disclosure agreement, and I was the victim. I, and my whole
lab, were the victims. And the lesson it taught me was that
non-disclosure agreements have victims. They're not innocent. They're
not harmless. Most programmers first encounter a non-disclosure agreement
when they're invited to sign one. And there's always some temptation --
some goody they're going to get if they sign. So, they make up excuses.
They say, "Well, he's never going to get a copy no matter what, so why
shouldn't I join the conspiracy to deprive him?" They say, "This is the
way it's always done. Who am I to go against it?" They say, "If I don't
sign this, someone else will." Various excuses to gag their consciences.
Nothing required Xerox to give Stallman the source code to the printer driver. And in a world without copyright, nothing would require Xerox to give Stallman the source code to the printer driver either. And it wasn't copyright that prevented Carnegie Mellon from giving him the source code - it was a separate contract - an NDA.
The four freedoms are guaranteed for open source because of copyright. Without copyright, the first freedom (with the access to the source code) for open source software is not possible. Copyright gives the author the ability to force others who use the software that they've licensed to be similarly open.
Consider this challenge - write a license on top of some public ___domain ( https://en.wikipedia.org/wiki/Public-domain_software#Public-... ) work that requires that I follow it and that the work that I do provides the four freedoms - that would prevent me from taking the code and repackage it in my own binary in a way that I'm not obligated to disclose to you or that you wouldn't be able to replace with your own library.
