logoalt Hacker News

adgjlsfhk1yesterday at 6:46 PM3 repliesview on HN

The main reason M3 took a long time isn't related to m3 itself, but rather that the asahi project took on a ton of tech debt to get M1/M2 working. M3 wasn't too difficult, but before taking on the additional tech debt, the Asahi team focused on getting all of their changes upstreamed to the linux kernel.


Replies

monocasayesterday at 7:20 PM

The main developer was also the target of a harassment campaign from a place that has pushed other targets to straight up suicide. That took almost all of their energy for the last year and they ended up quitting.

show 1 reply
norman784today at 8:05 AM

AFAIK they also were focusing on upstream the changes into the kernel [0], because the amount of downstream patches they were maintaining were making the work harder and harder.

[0] https://asahilinux.org/2025/10/progress-report-6-17/

tgtweakyesterday at 7:01 PM

Prognosis is then that work for m4/m5 should be relatively straight line now that refactoring is done?