Apples licenses for these will include very strict NDA clauses that make it impossible for apple to share the documentation they are provided but that vendor.
I don't want my speakers to stop working because I stopped paying subscription.
I say this as a longstanding iPhone user, and up until recently, Mac user.
Sometimes backwards compatibility is preserved even to the point of preserving bugs (especially if the companies/apps depending on it are large):
https://www.triplefault.io/2017/07/breaking-backwards-compat...
https://arstechnica.com/gadgets/2008/11/ars-investigates-doe...
So why can't we just allow them to keep making those changes, but still have to document them? I'm sure they document them internally anyway.
For example, the tax could be 1 cent per page per day which is non-public.
It would apply to source code, images, or anything else that might be reasonably printed on a page.
Then companies could pay the government to keep their employees work secret, or publish it.
It should help innovation as far more work done by humans gets made available for others to build from.
It's only companies who have fully closed tech will have to pay the tax, and really that tax is compensating the rest of the country for the work and knowledge that company wants to keep secret.
Right now increasing numbers of things are, "works until it doesn't" and that imposes risks and costs to everyone.
Perhaps those get high enough to warrant legislative solutions.
Right to repair. Hasn't happened because it's not a right yet.
Alternatively maybe anti trust, since using your monopoly on hardware to get a monopoly on software which is the essence of anti trust anyways. Hasn't happened because anti trust enforcement is really weak. Probably also doesn't force documentation.
Alternatively copyright and patent misuse, which is using your government granted monopoly on creating the exact hardware (copyright), or some of the features in the hardware (patents) to get a monopoly in an adjacent area (running software on that hardware) voiding the copyrights and patents. Hasn't happened because while the law exists (in common law) the courts apply it very conservatively. Also probably doesn't get documentation, just the right to run things on it.
Alternatively an interpretation of the quid quo pro of intellectual property (i.e. you disclose something in exchange for a temporary monopoly) being interpreted more strongly, such that you have to disclose the details of the internals to get intellectual property rights. Hasn't happened yet because today the quid quo pro isn't interpreted that strongly.
The interactions between a silicon chip and software drivers has nothing to do with right to repair. Never has been.
> Alternatively maybe anti trust, since using your monopoly on hardware to get a monopoly on software
Apple doesn't have a monopoly on any hardware, except insofar as any company has a natural monopoly on their own products, as made explicitly legal by copyright and patent laws.
Furthermore, one has to remember that there's a world outside of commodity PC hardware. The notion of hardware and software being separate is the rare exception, not the rule. Other than commodity PC computer hardware, nearly every product sold is both software and hardware bundled as a unit, with no marketplace expectation of end users replacing the software with an alternative. Whether you're talking about a car, washing machine, television, digital camera, microwave oven, garage door opener, CD player, indoor-outdoor thermometer, label printer, or an air conditioner, the software that comes with it is seen as part of the product.
In fact, this is even true for many computer components—companies like Nvidia aren't being any more helpful about their GPUs as Apple is with theirs.
Apple's computers straddle an interesting boundary between consumer devices and commodity PCs. But make no mistake, Apple isn't obligated to do anything here. You're not entitled to something because you want it.
> using your government granted monopoly on creating the exact hardware (copyright), or some of the features in the hardware (patents) to get a monopoly in an adjacent area (running software on that hardware)
Obviously legal. See above.
> Alternatively an interpretation of the quid quo pro of intellectual property
Obviously legal. See above.
Well, that's perhaps because that interaction's importance for the functioning of ubuquitous things in life is a relatively recent thing. I don't understand why there's supposed to be some fundamental reason why we can't change our laws to encompass also the right to repair software, or to the right to repair the interactions between hardware and software. Sure, these things aren't rights today – but who's to say we can't make it so?
Software bugs... you could reasonably end up with a right to fix them given the current direction of right to repair lobbying. And that right might include the right to documentation.
> Apple doesn't have a monopoly on any hardware, except insofar as any company has a natural monopoly on their own products, as made explicitly legal by copyright and patent laws.
Which is to say they have a monopoly...
Anti trust never makes having a monopoly illegal, it makes exploiting that monopoly to gain further monopolies illegal. It doesn't care about where the monopoly came from.
It does care about the kind of monopoly, current anti trust rules probably don't consider the monopoly Apple has from copyright and patents on hardware to be of the right category (to cover an entire market)... but that could easily change.
> Obviously legal. See above.
On the contrary...
https://en.wikipedia.org/wiki/Copyright_misuse
https://en.wikipedia.org/wiki/Patent_misuse
> Obviously legal. See above.
Yes, I agree under current definitions, but it would be a reasonable way for the laws to evolve. It is very similar in nature to the existing limits on patents, for example: https://www.nytimes.com/2003/03/06/business/university-s-dru...
Sure, but by that definition every commercial product constructed from multiple parts has a monopoly over all their components. Starbucks has a “monopoly” over what coffee is sold within Starbucks cups. Sorry, but I just can’t take that kind of argument seriously.
> current anti trust rules probably don't consider the monopoly Apple has from copyright and patents on hardware to be of the right category (to cover an entire market)... but that could easily change.
Copyright and patents are the very definition of a legal monopoly. I don't think you're being serious.
You're right, my reply there was poorly worded, fortunately you seem to agree with the point of the reply anyways since you say
> Copyright and patents are the very definition of a legal monopoly.
Which really is just the point.
However I am being entirely serious that there is more that not all monopolies implicate current anti trust law. Whether or not they do depends on whether or not they're a monopoly over the entirety of a market, not over a certain invention (patent) or copying a certain work of art (copyright).
You can see that at play in the current Epic v Apple case for instance. It's unambiguous that Apple has a monopoly over distributing apps to iPhones, it is ambiguous over whether the relevant market here is iPhone users, and therefore whether or not anti trust law applies.
Samba was able to get documentation for SMB/CIFS this way.
Or to put it less insolently: I've learned my craft by reverse engineering; as a auto-didactic tool it's a primary learning tool, definitely beats reading the manual.