I would prefer for the GPL and other copyright licenses to be unenforcable; unfortunately that isn't the case. So I prefer not to BSD-license my works because then copyright could be used against me to take my rights from me.
Can you elaborate on this point? I don't know what you're referring to.
e.g. I write a BSD-licensed song, and someone remixes that song and says that I cannot copy the remixed version.
Which has been stated before in this comment thread. If we abolish copyright, GPL is not needed. If we keep copyright (and thus accept the concept of derivative copies effecting the author), then GPL request freedom.
Please pick one. We should not cherry pick the arguments depending if one is talking about copyright or GPL. The same argument can't be false and true at the same time in the same mind.
Whereas when copyright is abolished, if I have the song I can copy the song. They cannot put terms on it that would withhold my freedom to do so. I don't really need the GPL anymore; I don't demand anyone's source code, just my freedoms with the knowledge and information that is available to me.
I agree with you about GPL now vs. ideally no copyright, but one thing that would definitely be lost is the ability to coerce releasing source code. Companies in a hypothetical no-copyright future could still keep source code secret, and still release compiled/obfuscated software. They could still take code others had released, make modifications, and then only release obfuscated binaries. They wouldn't be able to sue if someone leaked the source code, but is that enough of a protection?
Personally, I'm willing to live with it, because I think in the long run people would rather share. But from, say, RMS's point of view, people are losing some measurable level of protection.
Legal requirements to share, would actually make it a burden to provide anything: If I give my friend this disk, am I legally required to give them something else along with the disk? If my computer is accessible on a network, do I have a legal obligation to make any source code that is accessible also available? What are the rules about that?
I think it's too messy. And honestly, if a kid writes a game, maybe they're embarassed about the source code... the law shouldn't require them to share that with their friends/teachers/etc.
Although there might be merit to regulations on industry / corporate actions, especially in so far as their works affect the public (voting machines, safety equipment: software that we might want to require keeps its source-code alongside binary distributions).
I'm much more comfortable with people keeping data to themselves in a world where they have less legal ability to prevent others from sharing it.
For "software" replace "food" and for "source code" replace "ingredients". You can cook whatever you want at home, but when you start selling food to people certain responsibilities kick in. If a kid is selling lemonade but is too embarrassed to tell you what's in it, would you drink it?
Would not "definitely" be lost. It's easy to imagine other regulation which coerces releasing source code (indeed more powerfully, as not relying on copyright holder to both choose the right license and enforce it), if indeed that is a socially valuable thing to do.
What FSF is particularly against, in this post, is combining, arguably completely separate, trademark laws, copyright laws, patent laws, and trade secret laws, under a useless umbrella term "Intellectual Property" which can be leveraged for propaganda purposes and is of little real use.
Under any copyleft type of regime, even if you remove copyright and replace with some other enabling law, you're still using legal controls to enforce rights management of bits and bytes.
Such would still be "using legal controls" (or more broadly "using policy controls", as in the case of procurement, which could be private) but not necessarily to "enforce rights management of bits and bytes". The legal controls could be for example around certification of a product: no source, no certification, no legally selling product. In that case the bits and bytes independent of a product on the market would be unregulated, not subject to forced transparency.
GPL forbids giving away infringing code as well.
Does your proposed regulatory regime also encompass forcing all open-source and hobby coders to get one of your licenses before they can enable the "download as ZIP" feature on their GitHub?
If you didn't have IP law at all, what you'd have is effectively public domain, without even the 'moral right' of attribution of authorship.
The kinds of systems you'd be able to build with that would resemble BSD codes, not GPL codes. This would suffice for open-source software, to be sure, but not for Free software with all the political trappings that it brings [1].
In much the same way as DRM aims to restrict what you can do with the bits and bytes of media and code in favor of the 'IP holders', copyleft aims to restrict what you can do with the bits and bytes of source and even binary codes in favor of the 'IP users'.
While the class of set of people benefiting from IP is different, it all still relies on IP.
[1] https://www.gnu.org/philosophy/why-copyleft.html