← Back to context

Comment by trueno

3 hours ago

wasn't there like a drive by maintainer rejection of something rust related that kind of disrupted the asahi project ? i can't say i followed the developments much but i do recall it being some of that classic linux kernel on broadway theater. i also wonder if that was a first domino falling of sorts for asahi, i legitimately can't tell if that project lives on anymore

6 comments

trueno

Reply
iurbwdj  19 minutes ago

It involved large parts of the Rust community, and the famous Rust developer Hector Martin (with an alter ego of Asahi Lina, a female vtuber, which he appears irrationally embarrassed about), harassing others.

Even Linus Torvalds called out Hector Martin.

https://lkml.org/lkml/2025/2/6/1292

> On Thu, 6 Feb 2025 at 01:19, Hector Martin <marcan@marcan.st> wrote:

> > If shaming on social media does not work, then tell me what does, because I'm out of ideas.

> How about you accept the fact that maybe the problem is you.

> You think you know better. But the current process works.

> It has problems, but problems are a fact of life. There is no perfect.

> However, I will say that the social media brigading just makes me not want to have anything at all to do with your approach.

> Because if we have issues in the kernel development model, then social media sure as hell isn't the solution. The same way it sure as hell wasn't the solution to politics.

> Technical patches and discussions matter. Social media brigading - no than\k you.

> Linus

https://archive.md/uLiWX

https://archive.md/rESxe

bayindirh  3 hours ago

IIRC, it was not about Rust vs. C, but a commotion rooted from patch quality and not pushing people around about things.

Linux Kernel team has this habit of a forceful pushback which breaks souls and hearts when prodded too much.

Looks like Hector has deleted his Mastodon account, so I can't look back what he said exactly.

Oh, I still have the relevant tab open. It's about code quality: https://news.ycombinator.com/item?id=43043312

  • chippiewill  1 hour ago

    That was a single message in a very large thread. It absolutely was not just about code quality.

    • bayindirh  1 hour ago

      Yes, that's the entry of the rabbit hole, and reader is advised to dig their own tunnel.

      I remember following the tension for a bit. Yes, there are other subjects about how things are done, but after reading it, I remember framing "code quality" as the base issue.

      In high-stakes software development environments, egos run high generally, and when people clash and doesn't back up, sparks happen. If this warning is ignored, then something has to give.

      If I'm mistaken, I can enjoy a good explanation and be gladly stand corrected.

      This is what happened here. This is probably the second or third time I witness this over 20+ years. Most famous one was over CPU schedulers, namely BFS, again IIRC.