How long until apple blocks this? They are famous for protecting their walled garden and hostility towards cross platform development tools.
What you are supposing is that they might choose not to enforce that until their own headset is shipping in volume. If anything, they are building a case against this person while at the same time analyzing their suitability to park their ass in a chair in Cupertino...then it will go to an exec who will decide the person's fate.
- Corellium Inc vs Apple Inc, D.C. Docket No. 9:19-cv-81160-RS: https://aboutblaw.com/7PK
If Corellium can livestream a virtualized version of iOS on non-Apple hardware, I'd wager Joe Shmoe can livestream an official dev envrionment to their VR client.
If you accept the Developer Agreement and receive protected materials under it, you cannot redistribute, publish or stream it because of case law, sorry.
I know it’s confusing because of all the little unethical assholes who hack apart every beta release and post about it on blogs run by morbidly obese grifter-enthusiasts, but it is actually quite simple —Apple can and does pick and choose who to enforce its agreements on, just as you may.
LLVM and clang are both cross platform
If either LLVM or Clang tried removing multiplatform support or totally relicensed itself, it would divide the community and make life hard for Apple. They could probably make WebKit a fully proprietary browser engine by rewriting the KHTML stuff, but what would they gain by removing features from an Open Source product they developed?
https://learn.microsoft.com/en-us/dotnet/maui/ios/hot-restar...
There's absolutely nothing Apple is doing to prevent you from developing on iOS from Windows or Linux. Much of the open source development they're doing is making it easier in theory. But in practice, there's just not enough people willing and interesting in putting in the work to set it up. Most iOS developers would just rather use the official tools. And why should Apple put in lots of extra work just to let people develop from other platforms? That's just never going to happen.
If you copy those libraries illegally to Linux, you can build for MacOS from Linux - so either Apple feels indifferent towards engineers building for MacOS or they want everyone to buy a Mac and compile release software locally.
What worse is Apple doesn't provide any server-specific hardware/software for automation - so it really does feel like Apple expects people to build release software on MacBook Pros or something.
It doesn’t make a big difference in practice, but is there such a clause in their license? I thought the limitation was on Apple hardware.
If so, you can build on Linux running on a Mac mini, for example.
The same terms cover usage of things like Rosetta 2, which cannot be used on Asahi Linux despite Linux running on Mac hardware.
I would love to use Linux build machines but the xcode requirements make it a non-starter...and its not for lack of effort.
Apple's MO is to keep some APIs for itself, making them unavailable to third-parties.
Even if you do conceivably have access to “private APIs” that are not documented, you still shouldn’t use them.
Trying to deconstruct this to understand better.
2 possibilities.
1. Supporting cross platform development tools is actually in Apple's interest/business and they are being stupid not to support them. But so far it doesn't seem like they are losing anything by not supporting it going by their financials.
2. Supporting cross platform development tools is not in their interest - in which case they are doing the right thing by doing what's good for their business.
So, where is the disconnect?
The fact that Apple has been successful in keeping a good reputation despite nickle-and-diming all developers working with their platform is only a badge of honor in the marketing world.