Live data from Hacker News

Resigning as Asahi Linux project lead

marcan.st

21–30 of 1001 posts

Re: Resigning as Asahi Linux project lead

#21
post #6

See also the response from the Asahi team: https://asahilinux.org/2025/02/passing-the-torch/

"Although you don't see those threads, search engines do. HN uniquely has a high page rank and low moderation, making it a prime target for bad actors to poison search results with abuse, bigotry, and nastiness. This isn't low-level trolling, but an organized attempt to destroy lives, including of developers in our communities."

Re: Resigning as Asahi Linux project lead

#22

I think if I was indicted by Linus and told I'm a problem over spreading awareness about a position on social media, I too would burn out pretty quickly. That's how you crush motivation. There's a deeper issue in open-source culture where harshness and gatekeeping drive away passionate contributors.

Not to mention stalkers ? Doesn't matter how much you love a community, one or two psychopaths can maybe it simply not-worth-it.

It's hard enough in physical spaces to remove abusers (usually the abused just stop showing up), I can't imagine there's an answer for preventing this kind of behavior in online spaces

Re: Resigning as Asahi Linux project lead

#23
First of all, yay Asahi — one of the great modern hacking / hacker stories in my opinion.

Second, what’s the drama? I read the blog, and I’m guessing that on top of being burned out, which sucks, Marcan didn’t like a kernel developer using the phrase “we are the thin blue line” implies he’s politically liberal, in the US sense. He then says he may have been toxic on Mastodon, which might have got him secretly canceled?

All that said, I found his assessment of downstream v. upstream economics (if you can’t successfully upstream you’re doomed to rebase off a massive patch list) pretty interesting. I think the way it is now is the only way that’s good for users — if downstream forks could somehow maintain viability longer term, we would be splitting, e.g. security budgets, performance budgets, etc. I get that it sucks for a group working to upstream, and I am in no way shocked to hear personal politics plays some role in success upstreaming — open source is largely a personal / social capital economy - I guess all that said, hopefully the new Asahi maintainers can work well across what seems like ideology bounds. Maybe?

Re: Resigning as Asahi Linux project lead

#24
post #6

See also the response from the Asahi team: https://asahilinux.org/2025/02/passing-the-torch/

"Although you don't see those threads, search engines do. HN uniquely has a high page rank and low moderation, making it a prime target for bad actors to poison search results with abuse, bigotry, and nastiness. This isn't low-level trolling, but an organized attempt to destroy lives, including of developers in our communities."

Funny how this aged, now. Trying to shame people on Mastodon? Totally valid. Trying to chew someone out on a private forum? Now it's an organized attempt to destroy lives.

Re: Resigning as Asahi Linux project lead

#25
post #3

It's a shame to see but inevitable when trying to get open software working on such a proprietary platform with so many hardware cut corners and incomplete/non-standard implementations. Just an insane amount of work of the most frustrating kind. What they did manage to do was incredible... but Apple is Apple.

My sense from the article was that it seems less of an Apple is Apple issue, and more of a Linux maintainers are Linux maintainers issue. The big problems listed are all interpersonal conflicts and a sense that the maintainers were making his life upstreaming Rust changes hell.

Re: Resigning as Asahi Linux project lead

#26
Damn shame, both for the burnout and for the project. I was talking to the team which laptops next to get and kind of everyone wanted something like Arm with battery and performance and there are only MBPs (except damn notch) out there. Except no one wants MacOS. And then there's Asahi. I said it might come down to exactly this, what's happening now.

Re: Resigning as Asahi Linux project lead

#27
post #15
post #3

It's a shame to see but inevitable when trying to get open software working on such a proprietary platform with so many hardware cut corners and incomplete/non-standard implementations. Just an insane amount of work of the most frustrating kind. What they did manage to do was incredible... but Apple is Apple.

This isn't an Apple issue. Maybe Linux on Apple is inherently more problematic, but the issue here came from Linux maintainers hostility towards Rust.

[flagged]

Re: Resigning as Asahi Linux project lead

#29
post #6

See also the response from the Asahi team: https://asahilinux.org/2025/02/passing-the-torch/

"Although you don't see those threads, search engines do. HN uniquely has a high page rank and low moderation, making it a prime target for bad actors to poison search results with abuse, bigotry, and nastiness. This isn't low-level trolling, but an organized attempt to destroy lives, including of developers in our communities."

Always funny to me to read something like that. HN has high moderation, one of the highest I've seen on modern fora, only a few steps below r/AskHistorians for example. I don't see this "abuse, bigotry, and nastiness" here and even if there are comments like that, they are quickly downvoted and dead.

Re: Resigning as Asahi Linux project lead

#30

Well that's unfortunate. It seems like there's a balancing act between the benefits of writing drivers in Rust (easier, more maintainable), and getting those drivers mainlined (apparently soul-destroying, morale killing), I wonder if the Asahi team is considering simply abandoning linux in favor of something more rust friendly (redox being an obvious candidate, but maybe one of the BSDs?). Given the narrow set of har…

> Given the narrow set of hardware they're aiming to support and that they're writing many of their own drivers _anyway_ (and so are not relying as much on the large # of existing linux drivers), that approach might be more viable.

They are relying heavily on mesa. I'd also assume that GNU stuff is also pretty essential.

Perhaps Android would be possible? It has a HAL that might be easier to work with than the raw linux kernel. The android devs have put in a lot of effort to make downstream driver development not painful. With android, they'd also still have GNU stuff available.

The big issue is non-linux will mean every single open source tool may have a compatibility problem. You also end up dumping a huge amount of capabilities (like running docker containers).

Post reply on HN