As an early adopter there was zero software I used previously that I couldn't ru...

rvz · 2026-09-13T19:19:21

You might need to talk to the power users both here and beyond HN.

Developers who use Docker on Mac, Android Studio, homebrew usage and usage on embedded devices all had persistent issues and had to wait months for the ecosystem to improve for full stable support without Rosetta, instead of workarounds that break on another update.

Musicians that use DAWs such as Ableton reported that their plugins did not work and had to stay on Intel Macs. Same with those who have hardware for their instruments that need device drivers for their instrument setups also had to wait several months.

So it only made sense for power users to wait for the M2 and higher until the software was fully supported on Apple Silicon.

ladberg · 2026-09-14T02:31:14

I would seriously bet that <1% of Mac owners have ever run (Docker|Android Studio|Ableton), and fwiw I used Homebrew just fine off the bat

"for full stable support without Rosetta" is moving the goalposts because Rosetta made >99% of all workloads "just work" in a completely transparent way

rvz · 2026-09-15T13:18:45

> I would seriously bet that <1% of Mac owners have ever run (Docker|Android Studio|Ableton).

It's a great move if the M1 is your first Mac and just use their machine to surf the web, write documents and emails.

It makes even more sense for existing Mac and power users to just wait.

> and fwiw I used Homebrew just fine off the bat

That is not true. They needed compatibility hacks + Rosetta and even required re-compiling the software for Homebrew to work correctly with workarounds on GitHub issues.

> "for full stable support without Rosetta" is moving the goalposts because Rosetta made >99% of all workloads "just work" in a completely transparent way

Nope. What I said was an expansion from: "the software was not optimized and did not work correctly for the M1 and you had to wait it to be ready" to "full stable support without Rosetta, instead of workarounds that break on another update." Which is the same thing as expecting, an optimal version of the software.

Again, your evidence is made up numbers, hilariously anecdotal (anecdotes are not evidence) and on a technical site are usually just be ignored and dismissed.