<story><title>Airyx OS</title><url>http://airyx.org/</url></story><parent_chain><item><author>PaulDavisThe1st</author><text>&amp;gt; source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it)&lt;p&gt;Hard to see how this can be done legally. The libraries (sorry, Frameworks) that make up the user-space runtime for macOS are all proprietary. There&amp;#x27;s no replacement for the most important parts of it.</text></item><item><author>3np</author><text>More information and motivation in the git repo[0], the link to which I didn&amp;#x27;t spot easily in the site header.&lt;p&gt;The main design goals are:&lt;p&gt;* source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it)&lt;p&gt;* similar GUI metaphors and familiar UX (file manager, application launcher, top menu bar that reflects the open application, etc)&lt;p&gt;* compatible with macOS filesystems (HFS+ and APFS) and folder layouts (&amp;#x2F;Library, &amp;#x2F;System, &amp;#x2F;Users, &amp;#x2F;Volumes, etc)&lt;p&gt;* self-contained applications in folders or a single file and a (mostly) installer-less experience for &amp;#x2F;Applications&lt;p&gt;* mostly maintain compatibility with the FreeBSD base system and X11 - a standard Unix environment under the hood&lt;p&gt;* compatible with Linux binaries via FreeBSD&amp;#x27;s Linux support&lt;p&gt;* eventual compatibility with x86-64 macOS binaries (Mach-O) and libraries&lt;p&gt;* pleasant to use, secure, stable, and performant&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mszoek&amp;#x2F;airyx&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mszoek&amp;#x2F;airyx&lt;/a&gt;</text></item></parent_chain><comment><author>3np</author><text>This is addressed in the README I linked to. Reimplementation of APIs is not legally sketchy. See Oracle vs Google.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.eff.org&amp;#x2F;cases&amp;#x2F;oracle-v-google&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.eff.org&amp;#x2F;cases&amp;#x2F;oracle-v-google&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Google_LLC_v._Oracle_America,_Inc&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Google_LLC_v._Oracle_America,_...&lt;/a&gt;.</text></comment>
<story><title>Airyx OS</title><url>http://airyx.org/</url></story><parent_chain><item><author>PaulDavisThe1st</author><text>&amp;gt; source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it)&lt;p&gt;Hard to see how this can be done legally. The libraries (sorry, Frameworks) that make up the user-space runtime for macOS are all proprietary. There&amp;#x27;s no replacement for the most important parts of it.</text></item><item><author>3np</author><text>More information and motivation in the git repo[0], the link to which I didn&amp;#x27;t spot easily in the site header.&lt;p&gt;The main design goals are:&lt;p&gt;* source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it)&lt;p&gt;* similar GUI metaphors and familiar UX (file manager, application launcher, top menu bar that reflects the open application, etc)&lt;p&gt;* compatible with macOS filesystems (HFS+ and APFS) and folder layouts (&amp;#x2F;Library, &amp;#x2F;System, &amp;#x2F;Users, &amp;#x2F;Volumes, etc)&lt;p&gt;* self-contained applications in folders or a single file and a (mostly) installer-less experience for &amp;#x2F;Applications&lt;p&gt;* mostly maintain compatibility with the FreeBSD base system and X11 - a standard Unix environment under the hood&lt;p&gt;* compatible with Linux binaries via FreeBSD&amp;#x27;s Linux support&lt;p&gt;* eventual compatibility with x86-64 macOS binaries (Mach-O) and libraries&lt;p&gt;* pleasant to use, secure, stable, and performant&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mszoek&amp;#x2F;airyx&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mszoek&amp;#x2F;airyx&lt;/a&gt;</text></item></parent_chain><comment><author>jhawk28</author><text>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).</text></comment>