Hacker News Reader

Comment by adgjlsfhk1 | Hacker News Reader

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.

View on HN

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.

   > The main developer was also the target of a harassment campaign from a place that has pushed other targets to straight up suicide.

Is this the Torvalds/Hector dispute that comes on the Google AI summary, or was this a three-letter agency type of harassment faced by Aaron Swartz?

Neither actually... It was an anti trans/kiwi farms brigade...

The Torvalds dispute probably came about in part because of defensive behavior triggered this brigade but was really unrelated.

Anti-trans hate.

Trans hate.

GP definitely meant the same thing, i.e. 'hate [that is] anti-transsexualism' to your 'hate [against] transsexualism'.

FYI, transsexual is an outdated term, with transgender being generally preferred instead :)

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/

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

Reply on news.ycombinator.com