6 comments

  • iceboundrock4 hours ago
    A general purpose Apple Silicon layer for x86-64 PCs. It is a UEFI boot program with an arm64-to-x86-64 translator, a Metal driver for NVIDIA GPUs and a model of Apple silicon hardware. macOS and most apps start, but it is slow and needs much more testing, as of v0.1.0
    • stingraycharles1 hour ago
      Is the intent to support running macOS on it, or rather for e.g. Linux that targets Apple Silicon?
      • perfsakuya1 hour ago
        To support running the Apple Silicon version of macOS on x86-64 PCs.
  • yjftsjthsd-h3 hours ago
    So, <i>basically</i> an emulator layer that doesn&#x27;t need a host OS? (I&#x27;m not really interested in running Darwin, but that&#x27;s a cool concept)
    • cromka3 hours ago
      &quot;An ahead-of-time and just-in-time compiler translates arm64e code to x86-64.&quot;<p>No, not the same, actually. It&#x27;s more of a Rosetta, but other way round, if I understand this right.
      • yjftsjthsd-h2 hours ago
        Rosetta is an emulator (or, I suppose, a series of emulators), i.e. a piece of software that makes a computer pretend to be another kind of computer. This is also a bit of lower level software that makes a (x86_64) computer pretend to be a different kind of computer (aarch64), in this case, by AoT and JIT translation, though that&#x27;s an implementation detail. What distinction are you trying to make?
        • stavros49 minutes ago
          This doesn&#x27;t emulate a computer so that code in another architecture can run, it translates the other architecture&#x27;a code to native code. It&#x27;s a small difference, but I guess it is a difference.
      • throwaway274481 hour ago
        Is this not how qemu works? Is rosetta not considered an emulation layer? For all its name suggests otherwise, I would certainly refer to wine as an emulator, and it also uses these techniques.
        • zbentley51 minutes ago
          Not to be That Guy, but WINE <i>doesn&#x27;t</i> use those techniques, and thus isn&#x27;t an emulator.<p>It lightly translates <i>binary formats</i> (Windows executables) into Linux-compatible executable code, and then runs that code against libraries that implement Windows APIs in terms of Linux underneath. It&#x27;s not an emulator in the same way that your libc isn&#x27;t <i>emulating</i> lockf(3) in terms of fcntl(2) underneath. In web-dev parlance, we&#x27;d call WINE a polyfill.<p>Rosetta and QEMU on the other hand <i>are</i> emulators--emulators, in this instance, being a term of art that implies interpreting bespoke meaning from machine code instructions written in another program. Some emulators translate instructions 1:1, some have optimized stencils, some (like Rosetta) have kernel support for emulating very quickly, and some (maybe like Rosetta; sources disagree) also have hardware support as well.
          • leidenfrost39 minutes ago
            Wine as a polyfill makes so much more sense
          • throwaway2744837 minutes ago
            &gt; It lightly translates binary formats (Windows executables) into Linux-compatible executable code,<p>Does this not involve transpilation? I guess I was grouping that in under dynamic recompilation and AOT techniques.<p>Regardless, I don&#x27;t think that there&#x27;s a benefit from defining emulation from an implementation rather than an empirical perspective. If it runs a chunk of code as if it were in a different environment, I&#x27;m kind of ok to call it an emulator. To the sibling&#x27;s point, a polyfill would also fit as an emulation layer here.
  • jamesy0ung3 hours ago
    I noticed Golden Gate still ships with an x86_64 kernel (not kernelcache), I wonder if this is any useful<p>james@Jamess-MacBook-Pro ~ % sw_vers ProductName: macOS ProductVersion: 27.2.1 BuildVersion: 26B131 james@Jamess-MacBook-Pro ~ % file &#x2F;System&#x2F;Library&#x2F;Kernels&#x2F;kernel &#x2F;System&#x2F;Library&#x2F;Kernels&#x2F;kernel: Mach-O 64-bit executable x86_64 james@Jamess-MacBook-Pro ~ % strings &#x2F;System&#x2F;Library&#x2F;Kernels&#x2F;kernel | grep &quot;Darwin&quot; @(#)VERSION: Darwin Kernel Version 27.2.0: Wed Oct 14 23:40:09 PDT 2026; root:xnu-13432.41.4~25&#x2F;RELEASE_X86_64 Darwin Kernel Version 27.2.0: Wed Oct 14 23:40:09 PDT 2026; root:xnu-13432.41.4~25&#x2F;RELEASE_X86_64 Darwin
    • vintagedave2 hours ago
      This is fascinating. If x64 isn’t supported in Golden Gate why is this present?
      • ykl55 minutes ago
        Rosetta 2 is still supported, and the way Rosetta 2 works requires that various system components that x64 apps might depend on also be available in x64. x64 code that is running as arm64 translated by Rosetta 2 can’t call into native arm64 code due to ABI differences, so Rosetta 2 must translate the x64 version of system libraries as well.<p>My impression was that this did not require the kernel though, just system frameworks, so I don’t know why there’s a full x64 kernel in there!
      • stingraycharles1 hour ago
        Not saying this is the reason, but we build and test and release our software on platforms nobody uses, as it catches rare compiler &#x2F; memory &#x2F; UB bugs we otherwise wouldn’t have (eg win32 and FreeBSD)
        • 1over1371 hour ago
          Lots of people use FreeBSD :)
    • ndiddy1 hour ago
      Reminds me of how some of the dev versions of Snow Leopard still boot on PowerPC.
  • schmeichel3 hours ago
    Huge. I have been desperately looking for a project like this to be able to use <a href="https:&#x2F;&#x2F;github.com&#x2F;seedds&#x2F;nxnative" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;seedds&#x2F;nxnative</a> to be able to play my copy of BOTW on IOS. Thank you for sharing this, I will be trying it this evening.
    • sneurlax3 hours ago
      Is this really needed? I got it working on macOS pretty easily without this. It&#x27;s all in private repos tho, not exactly easy to share by URL unless you&#x27;re willing to sign up for a gitea.
  • rbanffy3 hours ago
    Sounds like a great use for those new Epyc processors with 256 cores…
  • orionblastar4 hours ago
    This repository needs a star and a follow. It stops Intel Macs from becoming obsolete, but it is slow and buggy.
    • code_duck2 hours ago
      Apple still supports the latest ones up to Tahoe, and probably security updates for a few years. You can install Windows 10 (no idea about 11) but that is only updated through next year. After that, there&#x27;s Linux, of course.
      • 1over1371 hour ago
        macOS does get <i>some</i> security updates for the non-latest version, but it does not get <i>all</i> security updates.<p><a href="https:&#x2F;&#x2F;arstechnica.com&#x2F;gadgets&#x2F;2021&#x2F;11&#x2F;psa-apple-isnt-actually-patching-all-the-security-holes-in-older-versions-of-macos&#x2F;" rel="nofollow">https:&#x2F;&#x2F;arstechnica.com&#x2F;gadgets&#x2F;2021&#x2F;11&#x2F;psa-apple-isnt-actua...</a>
    • rbanffy3 hours ago
      I don’t think there is anything that can make Intel Macs not obsolete. Embrace it - that’s their charm and you should use them as they were intended to be used, and experience them as they were designed, as artifacts of their time.
      • LeFantome1 hour ago
        No thank you. They can sit in a museum 30 years from now. Today, they are still amazing and productive machines (once you get macOS off them).
      • iceboundrock3 hours ago
        I installed CachyOS on my MacBook 16,1, and it feels much faster than with macOS, but the D side is still hot though.
      • bigyabai20 minutes ago
        Many (most?) Intel Macs still receive microcode updates, Mesa support and recent kernel changes.<p>The only obsolete part is macOS, which is removable.