Homebrew not supported yet ... it don't feel real

[NeVixm]

In my daily life, I'm a full-stack developer, and it is not feeling right that homebrew is not supported for the new M1 processor.

How should I run now my react apps etc... Have anyone here a solution? VSCode is supported, thank god!

 

[ct2k7]

Run homebrew from a terminal that opens under Rosetta

 

[Tuscape]

I followed the steps at https://soffes.blog/homebrew-on-apple-silicon so now "brew" is for arm stuff and "ibrew" is for intel stuff. Works very well so far.

 

[Internaut]

Thanks for this. I’m probably going to try going it without brew, for now. Means having to get a better understanding of where s*** is supposed to go, paths and stuff :-/. I’m expecting a thoroughly buggered sense of order (long time sudo apt get user, so brew was instinctive).

 

[haralds]

I am using the brew/ibrew approach outlined above. So far the native brew provided all the commands I needed. ibrew list is empty. Subversion, carthage, etc. - all ported.

 

[Internaut]

Have Maven and Gradle been ported? A Google search reveals nothing (but I'm surprised Subversion has been ported already - support for that is all too often an afterthought these days).

 

[dvdrl]

Have Maven and Gradle been ported? A Google search reveals nothing (but I'm surprised Subversion has been ported already - support for that is all too often an afterthought these days).

Aren’t Maven and Gradle written in Java? That means that you‘d only need a ported Java VM.

Stuff like subversion probably didn’t need any porting, as these things have been built for different unices and processor architectures for a long time and are highly portable. It’s possible that some x86 specific optimisations aren’t compiled in.

 

[Internaut]

Aren’t Maven and Gradle written in Java? That means that you‘d only beed a ported Java VM.

Stuff like subversion probably didn’t need any porting, as these things have been built for different unices and processor architectures for a long time and are highly portable. It’s possible that some x86 specific optimisations aren’t compiled in.

Ahh, yes. Actually very true. I have them running natively already because I have the Azul build for Apple/ARM up and running.

 

[Polly Mercocet]

Ruby, which is what Brew uses, has already been ported over to ARM. There is no *official* support yet basically because they're still testing packages for compatibility. This is why the official advice from the devs is to run Terminal under Rosetta 2.

Personally I am holding off for a bit simply because I'm not sure how this slightly hacky solution will leave me once official ARM support is included in Brew binaries. It looks like I'd have to uninstall Brew as well as all Brew packages then reinstall them again in a normal (non-Rosetta) Terminal. I'd rather just wait for things to be official so there's no headaches down the road.

But that's just me. I don't foresee support taking too long considering it's only a matter of testing packages, not a whole port that still needs to be done.

 

[leman]

Personally I am holding off for a bit simply because I'm not sure how this slightly hacky solution will leave me once official ARM support is included in Brew binaries. It looks like I'd have to uninstall Brew as well as all Brew packages then reinstall them again in a normal (non-Rosetta) Terminal. I'd rather just wait for things to be official so there's no headaches down the road.

The nice thing about Homebrew is that reinstalling just takes a couple of minutes 🙂 But I definitely agree that your approach is the sensible one.

I ordered an M1 machine because I look forward to the hacking and because there is a certain pleasure in owning a device that gets faster and faster as software support improves.