Ghidra worked out-of-the-box in Rosetta and natively with a few simple build system tweaks, tricore-qemu was trivial to build, Mono is working, VSCode is nicer than ever, and CrossOver Wine (in Rosetta) even works great for running Windows-only toolchains. It's rough around the edges and whether or not your use case is successful is definitely very specific, but for my personal hobby projects (ECU reverse engineering), it's been an excellent tool. Saying 'there is no point in getting an M1 MacBook' is probably what's garnering you the downvotes. Once again, Another thing the M1 Macbook early adopter hype-squad omitted as they are still suffering from a sunken cost while I get a second or third generation Apple Silicon Macbook which will be much more optimised and by then the ecosystem will be better supported out of the box.

What is the point of using this when it clearly says it has missing functionality and is less functional than the android emulators found on macOS on Intel? This is not even available in the stable release of Android Studio and is still not production ready. When building, it may be faster to start then cancel the Python triggered build and then reissue ninja -C objs install/strip versus letting the Python triggered build finish. Popup on startup about not being able to find the ADB path (ADB will still notice the emulator if you have it installed though) Downvoters: So this is not true? Time to cut through the hype.

Android studio m1 apple