4 ms·

You would need to reverse engineer what the frameworks are supposed to do and provide new implementations. (You can see all their external APIs) This is what Go

You would need to reverse engineer what the frameworks are supposed to do and provide new implementations. (You can see all their external APIs) This is what Google did with Java on Android. The courts currently view this as legal (Google v Oracle).

cable2600 5y ago
The core of MacOS is Darwin which is open source. Based on the MACH/XNU kernel and *BSD. So any MacOS clone would start with using Darwin code.
- saagarjha 5y ago
  Emulating macOS at the Darwin layer is not necessary and often not advisable (see: GNUstep).
  - PaulDavisThe1st 5y ago
    The goal was "source code compatibility with macOS applications".
    - saagarjha 5y ago
      Most Mac apps never call into the Darwin layer directly.
      - PaulDavisThe1st 5y ago
        Lots of macOS applications need to drop to a few Darwin related features from time to time, if only to work around bugs in the frameworks. In addition, lots of applications run on macOS that use POSIX APIs, which are (typically) implemented in Darwin and not in the user-space frameworks. But yet, I misunderstood the GP comment, and what I said was not really appropriate in that context.