From @dmitshur's comment in #47578 (comment) (thanks!)

To my knowledge, likely out of device fingerprinting concerns, browsers don't officially expose the underlying system architecture, so web pages typically look the same regardless of whether the user is visiting from a macOS device with an Intel or Apple CPU.

I'm aware there are some workarounds, like getting the device GPU vendor name and checking for a known substring that M1 devices have. An example of that being used is the VLC home page, https://www.videolan.org/, which changes its default download link using that heuristic.

So, I'm not sure that we should try to add automatic detection. If we make both downloads Featured, they should be equally visible and hopefully easier to pick the intended one.

I think detecting the underlying system may be difficult. Then, I think we should investigate alternatives

• Offer "Universal" as the default, but also provide "Intel Chip" and "Apple Silicon" options.
• Present both options for MacOS users: Either drop-down menu or two different download block. If we take this route, add first-time go user-friendly description to refer to each architecture (I rarely see darwin-arm64 or darwin-amd64 outside the go community)