Live data from Hacker News

Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

notion.so

101–110 of 148 posts

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#101
post #86

Earlier quoted context omitted.

Is this actually GDPR compliant as it is?

If it doesn't ask for consent and stores PII then no, it's not.

It's a Google Analytics client (using curl), so they punt on the GDPR issue to Google, who has a little "scrub client IP" checkbox in GA, which Homebrew has checked.

This is fine, because Google can be trusted to come into possession of your uniquely-identified tracking data, and then immediately delete it, without letting military intelligence log it in the process. They have no reason to share it (other than the legal compulsion that FAA 702 provides) or keep it around, as it would not profit them in any way (other than their multibilliondollar advertising business).

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#102
post #86
post #64

Earlier 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…

Is this actually GDPR compliant as it is?

  Homebrew gathers anonymous aggregate user behaviour 
  analytics using Google Analytics. You will be notified the 
  first time you run brew update or install Homebrew. 
  Analytics are not enabled until after this notice is shown, 
  to ensure that you can opt out without ever sending 
  analytics data.
That is from the Homebrew site.

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#103
post #68
post #46

Earlier quoted context omitted.

macports is a better homebrew-killer IMHO. Follows MacOS guidelines and frameworks, integrates with the MacOS way in terms of launch agents etc.

Macports doesn’t install for me with no error messages.

That's very odd. Did you try to run the installer from a terminal to check if it says something?

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#104

There'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... )"

Stickiness of architecture is a change from how Rosetta worked in the PowerPC to Intel transition: in macOS Big Sur child processes will prefer the arch of the parent process if one is available to maximize compatibility. So for example launching x86_64 sh will cause a python invocation from that shell to also be x86_64. The "arch" utility is your escape hatch to switch the preferred arch for the spawned process and…

Would be easy to make iTerm2 launch arch -x86_64

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#105
post #63

are there any benchmarks of x86-64 homebrew ports running under rosetta2 vs the last generation of intel macs? how about stuff like python, webservers or java apps running in x86-64 linux docker containers? very curious what the effects are of the new arch on common developer use cases. (without having to recompile/rebuild everything for apple arm)

Not for Homebrew but some benchmarks here: https://www.anandtech.com/show/16252/mac-mini-apple-m1-teste...

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#106
post #80
post #55

Earlier quoted context omitted.

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…

Python 3.8 for example got moved from the base OS install to Xcode's command line toolset. For developers, that doesn't change much.

It's in the base OS actually.

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#107
post #55

Earlier quoted context omitted.

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…

I can imagine many existing tools still rely on the commands being directly accessible on PATH, and Apple may be reluctant to break them outright even that’s the goal. They are declared deprecated so people would refrain from using them for new things, and move old things away from them. That’s basically what deprecation means in software, as I understand it. Those commands wouldn’t be called deprecated if Apple brea…

Right, but in that case I would not expect them to upgrade Python to 3.8.

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#109

Earlier 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.

Does this plan include differentiating at the Casks as well? (Thanks for the work on homebrew, I live by it - its key to my use of MacOS ..)

Casks are typically precompiled application binaries, and I assume most applications (that choose to support M1) will be Universal Binaries soon. Casks would not need to change anything.

Re: Run x86 Apps (including homebrew) in the Terminal on Apple Silicon

#110
post #106
post #80

Earlier quoted context omitted.

Python 3.8 for example got moved from the base OS install to Xcode's command line toolset. For developers, that doesn't change much.

It's in the base OS actually.

Nope. Python2 is inbox, but Python3 redirects to the Xcode/developer tools copy.

  % sw_vers
  ProductName: macOS
  ProductVersion: 11.1
  BuildVersion: 20C5048k
  % ls /Library/Python/                  
  2.7
  % ls /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/
  Headers  Python3  Resources Versions
  % ls /System/Library/Frameworks/Python.framework/
  Python  Resources Versions
Post reply on HN