Earlier quoted context omitted.
> I suppose you're not a big fan of puppies then? > right to repair This has absolutely nothing to do with copyright except that you lump them both together under "freedom". That's your arbitrary grouping, not mine. You're free to use tape to fix your copy of Harry Potter if it rips. Nobody has ever disputed that. You're not free to mass produce copies of it and sell it for profit. I am arguing that it's okay that an…
> Computer programs are radically different from literary and artistic works. It’s unsurprising that laws that were designed for paper books are less than a great fit for software. Indeed, software probably shouldn’t be eligible for copyright protection at all. Recipes which are another species of algorithm aren’t accorded copyright protection because they are simply a set of instructions. > Perhaps we should all wor…
Yet Recipe Books (particular curated collections of recipes) are afforded copyright protection. If your argument is that copyright should not be given to general algorithms like the FFT, new methods of fast matrix multiplication, the Carmack Hack, etc., then I actually completely agree with you. In all art, there is a level too granular to be copyrightable. In music, it's chord progressions and simple, obvious melodies. In books, it's common idioms and simple sentences like "Terrified, he ran." In programming, it's basic/common algorithms, design patterns, and commonly used control flow. None of that should be afforded copyright protection, and I hate seeing the frivolous lawsuits that come up in all those fields based on these trivial similarities.
Besides, modern Haskell or C# or TypeScript or Rust code is not simply a set of instructions. You could argue that assembly language is. But the vastly different ways to express the same logical things in different languages, including comments, naming conventions, clever tricks, etc. all together comprise a body of artwork (yes, artwork) that is clearly copyrightable.
For what it's worth: IMO code should not be eligible for patent protection. It's actually possible for someone to dislike software patents, support right to repair, and also support copyright protection for programmers.
> you should be paying the users of your proprietary software because you are observably reducing the value of their computer compared to a free alternative
It's hard to argue I'm straw-manning you when you make such obviously outrageous statements. This statement is like a caricature of everything I'm claiming the FSF is.