4 ms·
To add to parent’s point, AS is a one way trip to Big Sur, with no viable alternative (no downgrade, no dual boot anymore) Then it’s not just big app companies
by hrktb 6y ago
To add to parent’s point, AS is a one way trip to Big Sur, with no viable alternative (no downgrade, no dual boot anymore)
Then it’s not just big app companies that need to adapt, homebrew and CLI short lived utilities will also need ARM compatible versions or we’ll be wrapping each individual command in a Rosetta 2 launcher.
It might not be that bad, but I’d sure want to wait and see how it pans out, as it doesn’t look like a trivial transition.
- nottorp 6y agoDoesn't homebrew compile in place anyway? Macports does if they don't have a binary package handy. And as for arm compatibility, most command line tools come from Linux where they've already been compiled for arm ages ago. So the CLI should be the least problem with Big Sur. Unless they somehow cripple it on purpose so you can't use common unix command line stuff any more.
- matwood 6y agoHomebrew is fine, and nothing about the CLI is crippled in Big Sur.
- hrktb 6y agoIt should all work fine eventually, even if not on day 1 at least after a while. But I think there will be a transition phase for edge cases. For ARM support for linux, my understanding is that pure server stuff is completely fine and battle tested, hobby/side peoject level utilities are a riskier bet. I remember hitting some of those on a rasberry pi a while ago, but then the situation might be way better already with all the buzz surroubding ARM nowadays. For reference the github issue tracking page: https://github.com/Homebrew/brew/issues/7857 https://github.com/Homebrew/brew/issues/7857
- mappu 6y agoThe Mach-O loader should transparently invoke Rosetta 2.