why do people keep using this marketing fluff word "Apple Silicon"? should just call it Apple M1
Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
71–80 of 148 posts
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#72Does Macports support Apple ARM? They have a Big Sur compatible version, so I'm inclined to think it can at least try compiling natively. https://www.macports.org/install.php
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#73Earlier quoted context omitted.
I looked through brew.sh. Apologies if I'm missing something, but I don't think I am. There's something really offensive about apple being too cheap to just pay some homebrew devs. And dumping the work of the arch swap onto charity effort.
I just linked you to the official page which shows what works and what doesn't work, and your response is that you're still right and everything works?
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#74Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#75There's also the "arch" command, to run commands under rosetta2 I just installed Homebrew on my new m1 MacBook Air with: $ arch -x86_64 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/in... )"
The "arch" utility is your escape hatch to switch the preferred arch for the spawned process and all of its children.
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#76Earlier quoted context omitted.
Homebrew maintainer here. We don’t officially support Big Sur yet, but installing it via Rosetta will cause it to fetch x86 bottles instead of ARM ones. At least, that’s the plan.
Please make Homebrew’s telemetry opt-in instead of opt-out. I encourage you to follow the good example of how Debian runs popcon (popularity contest). By having your default be assuming user consent to surveillance, you have produced spyware that reports a user’s track log history to Google via IP geolocation and a persistent unique machine identifier included with the request to Google Analytics every time the user…
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#77I wonder if Nix on macOS could become a better homebrew-killer by supporting Apple Silicon first. We already do aarch64-linux natively and some iOS cross compilation, so that should give us a head start.
Being a lonely maintainer means I’m a bit (a lot) late on package versions and some areas are hacking, but it works on Big Sur already. But then again I’m also most probably the sole user and only target audience given the popularity of alternatives.
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#78Earlier quoted context omitted.
Please make Homebrew’s telemetry opt-in instead of opt-out. I encourage you to follow the good example of how Debian runs popcon (popularity contest). By having your default be assuming user consent to surveillance, you have produced spyware that reports a user’s track log history to Google via IP geolocation and a persistent unique machine identifier included with the request to Google Analytics every time the user…
Would you mind sharing how you disable that?
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#79I wonder if Nix on macOS could become a better homebrew-killer by supporting Apple Silicon first. We already do aarch64-linux natively and some iOS cross compilation, so that should give us a head start.
macports is a better homebrew-killer IMHO. Follows MacOS guidelines and frameworks, integrates with the MacOS way in terms of launch agents etc.
Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon
#80Earlier quoted context omitted.
Apple deprecated direct access to system-provided interpreter installations, which is a good thing. Interpreter support was not and will not be a problem, the implication of the deprecation is you should install your own copy of those interpreters instead.
Yes, I understand that we can and should always install our own, and I have for years either with Homebrew or Conda. (Actually most of my development is python on Linux via Vagrant). But on the M1 Mini, out of the box, you can open Terminal, and python3 launches the Python 3.8 REPL. Python 2.7 also launches out of the box. So, can you explain what you mean by "direct access" not being allowed? I'm not following your…