I don't see any legitimate existential risk for the devs or project?
ToS are only relevant for those who are a party to it - this is the users responsibility.
Historically, while Apple is protective of their IP they have not been acting like Nintendo with regards to emulators and hackintosh and such in court.
Weird concern unless you can point to actual threats or precedence.
> Weird flex
On the contrary, it's a legitimately useful feature that has popular demand.
In the article it's mentioned a docker version of this got a dmca takedown.
Apple does not license MacOS for use on hardware they don't sell. It can be argued this feature does not have any legitimate functionality.
At the same time, if you must decide to violate the license terms of OSX it should be done in a separate fork.
GitHub will just delete the whole project if Apple ever catches wind of it and complains. The DMCA isn't exactly a court proceeding, usually the content host determines the juice isn't worth the squeeze.
That sucks for everyone who decides to use it for legitimate purposes.
To be blunt Apple gate keeps there software and build tools behind expensive hardware. If you disagree, use different software.
Edit: Given I'm 90% sure they aren't running Arm OSX anyway, this is going to be irrelevant in about 2 years.
> I'm a little confused as to why projects like this support macOS since at a minimum it's a TOS violation.
As others have pointed out, emulating macOS is only a ToS violation if done on non-Apple hardware, and this tool supports macOS. There is a legitimate usecase of running macOS VM on macOS.
Sure, you could use some apple-provided emulation tool instead of QEMU but that's a matter of choice, not a violation of ToS.
Disclaimer: I'm not a lawyer. This is not legal advice.
Doing stuff like this, and integrating it into the main project puts the whole thing at risk.
The only real reason to MacOS is it's tight integration with Mac hardware.
Weird flex...