Earlier quoted context omitted.
Look, you might be right. But you might be wrong. We don't know for sure. One of my first jobs was in infosec, and there was a sign above one of the senior consultant's door quoting Hanlon's Razor: "Never attribute to malice that which is adequately explained by stupidity". That quote is right. There's so much going on at any medium-to-large organisation, from engineering to politics and personalities. All that multi…
Your reply makes sense in a vacuum, but in reality we have the context of having seen Apple comply with regulation maliciously before, so we do know for sure that there's no macOS in the sdk because they weren't forced to by regulation.
Unless you have insider knowledge, we don't know anything for sure here. Apple isn't a person. Apple doesn't have a single, consistent opinion when it comes to openness and EU regulation. (And even a person can change their mind.) All we know is that some teams at apple responded in the past to some EU regulation with malicious compliance. That doesn't tell us for sure what apple will do here.
Apple is 165 000 people. That's a lot of people. A lot more people than comment regularly on HN, and look at us! We don't agree about anything. I'm sure plenty of apple's employees hate EU regulation. And plenty more would love to opensource everything apple does.
That sort of inconsistency is exactly what we see across apple's product line. The Swift programming language is opensource. But SwiftUI is closed source. Webkit and FoundationDB are opensource. But almost everything on iOS is closed source. Apple sometimes promotes open standards - like pushing Firewire, USB and more recently USB-C - which they helped to design. But they also push plenty of proprietary standards that they keep under lock and key. Like the old 20-pin ipod connector, that companies had to pay money to apple to be allowed to use in 3rd party products. Or Airdrop. Or iMessage. AFS (apple filesystem) is closed source. But its also incredibly well documented. My guess is the engineers responsible want to support 3rd party implementations of AFS but for some reason they're prohibited from open-sourcing their own implementation.
We don't know anything for sure here. For my money, there's even odds in a year or two this API quietly becomes available on macos, watchos and tvos as well. If you "know for sure" that won't happen, lets make a bet at 100-1 odds. If you're sure, its free money for you.