Earlier quoted context omitted.
There is no "right to repair" without the 4 freedoms. You can't "repair" if you cannot inspect and run (0 and 1), and your repair is fundamentally meaningless if you cannot communicate it (2 and 3).
> your repair is fundamentally meaningless if you cannot communicate it (2 and 3). I have spent significant amount of time working around bugs and limitations in proprietary software that could have been fixed easily otherwise, and simply being able to fix it for myself or our company would absolutely be beneficial. This is so staggeringly blindly obvious that it pains me that this is even a point of contention. Of c…
That's basically the old Unix model, in practice it was unsatisfactory to the point that... people just wrote their own Unix and made a point that fixes should be public - and we got GNU.
Companies could give you the old Unix model tomorrow, if they so wished; but it's effectively lose-lose, because they don't gain anything meaningful (if anything, their support costs are increased by having to deal with thousands of potential user-introduced variations) and you don't gain anything meaningful either - your fix is forgotten the minute you move on and you won't be able to use it with your next employer.