Although this previous feature request has been marked as closed or completed, regarding the growing architecture shift on Mac and regarding the limited performance, this would still be highly appreciated.
This is the only remaining Intel-only app I regularly run on my Mac. Hoping for a native version sooner rather than later!
Just thought that it’d be a good idea to point out that the next beta of Local has a native Apple Silicon download. So this is about to be dealt with.
Pretty sure you meant current beta, Local Beta 6.5.0
Even the latest Local 6.7.0 is still not fully native: nginx, mysqld, and mailhog are all still Intel binaries. What is the status of an update for Local that is fully Apple Silicon native? As it stands, Local is one of just two apps on my Mac that remain at least partially Rosetta-dependent. I presume this is still being worked on, but as more and more updates to Local ship without mention of this in their release notes (and after double-checking in Activity Monitor), and as we draw ever closer to the next WWDC where we may hear about how much longer Rosetta has to exist, I just want an update on the progress of fully completing this feature request.
Hey @alexclst! I just wanted to let you know I’ve shared your comment with our Local Devs. This is something that has been raised inside and outside of the forums and they have had it on their roadmap already. As you noted, WWDC could end up creating a priority shift for this and moving timetables. For the time being, we don’t have a specific ETA or update to provide, but I just wanted to you let know that this hasn’t been forgotten about. We always appreciate the insight of our community!
Second that. First of all I want to express my gratitude and that I’m really thankful for the software in the first place!
Besides Rosetta-dependency especially mysqld uses a lot of RAM.
What I’m just wondering, aren’t these just dependencies (already available as ARM) that would just have to be properly linked at compiling?
Is this feature for Apple Silicon native support still actively on your development roadmap? Since universal binaries for nginx, mysqld, and mailhog should be readily available, it leaves me wondering what specific challenges are preventing their integration into Local. Is the issue related to testing and stability, or are there other technical complexities that the community should be aware of?
Thank you for your ongoing efforts and hard work on this matter. We all appreciate it.
Hey @localster - thanks for reaching out! Yes, it is still actively on our development roadmap. I shared a recent update in another thread last week: macOS Ventura WP-CLI fatal error TypeError: implode() - #20 by austinwendt
The issue is in testing and stability, and frankly juggling those updates with other changes we’re working on in the application with a small team. The portion of the user base on Apple Silicon is still relatively small compared to Intel Mac and Windows, and we’ve been focused on issues/features that are cross-cutting recently. That said, it is coming
Maybe a naive question on my end - Is the concern with running Rosetta performance? Are you seeing slower speeds in Local than you would like? It is pretty snappy on my personal M2 (I use an Intel Mac for work yet). Or is it more about the principle of not wanting Rosetta running on the machine? And if so, why is that?
One detail I’ll add that I forgot in my last post - there is some technical complexity that we’ll have to account for. Local uses
sudo prompt in several places to take actions in Local today. Sudo prompt is not compatible with Apple Silicon, so we’ll have to identify an alternative and plug that in before we can just drop in new binaries.
@austinwendt I can answer for myself… It is somewhat two-fold:
- As you say, some of it is principle and the fact that Local is all that still uses Rosetta on my Mac, although I know that I see no noticeable performance issues on my M1 Mac mini, so I’m not too worried. I just know, in part from having some of them installed via Homebrew, that all the remaining “lightning services” do indeed have ARM versions available.
- I know that someday Apple will drop Rosetta 2 entirely, maybe not soon (it is still in Sonoma, indeed Local itself works great there, and a few Intel Macs are still supported), but someday. I don’t want to see Local die with Rosetta. So I hope that work continues, and you all are prepared to jump into prioritizing this much higher over a summer as soon as Apple announces (likely at some WWDC) that Rosetta will be dropped from that next Fall’s update. But that won’t likely be for at least a year or two.
I do have one question about your latest comment: What is
sudo prompt? If the underlying lightning services are native, and as far as I know the main app plus PHP are, where does another tool come in? Certainly Local is doing just fine asking for my admin credentials to edit /etc/hosts and such. Is that part actually not Apple Silicon-native yet?
Awesome… M1 and M2 is Stunning Processor
This probably just refers to the sudo prompt regarding permissions when executing commands.
Thank you @austinwendt and sorry for my late reply.
I’m very happy to hear that this is still on the roadmap.
And yes it appears to actually affect performance to a noticable degree, especially regarding mysqld.
I’ve tested this on M1 and M2.
Yet as you know it’s difficult to put this in perspective as this actually depends a lot on individual amount of RAM.
Rosetta 2 tends to use quite a lot more RAM.
So if you have a big databases with heavy mysqld usage, you might using your Swap sooner, which affects performance, as well as tear on the SSD.
Quick perspective update from me as well: I’ll gladly admit it’s mostly about having a “clean” macOs, i.e. without any Rosetta overheads. But it’s also that when I compared using WP backend of the same site using Laravel Valet (fully Apple Silicon-native since what feels like forever) vs. LocalWP (only PHP is native), Valet was significantly faster – which is why I install LocalWP from time to time, quickly test it, but then stay on Valet.
Reasons to switch back to Local would be: a) I’m very much a GUI person and don’t have much love for the gazillions of services Brew installs and presumably runs and b) LocalWP generally does a lot right, stuff like save site to cloud or even save DB to file when stopping a site are sorely missed on bare-bones Valet.