Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Resigning as Asahi Linux project lead

marcan.st

Post reply on HN
Print view View original

531–540 of 1001 posts

Re: Resigning as Asahi Linux project lead

#531

Post by rekoil »

rc00 wrote: post #459
rekoil wrote: post #287

Earlier quoted context omitted.

Which is a moot point because the agreement right now is that Rust code is allowed to break, so the C developer in question can just ignore Rust, and a Rust person will take care of it for them.

As of today, the burden is uncertain and the Rust crowd has not been fixing things quickly enough since they are manual fixes: https://lore.kernel.org/rust-for-linux/20250131135421.GO5556... > Then I think we need a clear statement from Linus how he will be working. If he is build testing rust or not. > Without that I don't think the Rust team should be saying "any changes on the C side rests entirely on the Rust sid…

> Does this help to explain the burden that C developers are facing because of Rust and how it is in addition to their existing workloads?

Yep, thanks!

Re: Resigning as Asahi Linux project lead

#532

Post by talldayo »

mschuster91 wrote: post #308
__turbobrew__ wrote: post #197

Earlier quoted context omitted.

Agreed, supporting apple devices is going to be a maintenance nightmare as it goes against the wishes of apple. At best, apple involuntarily makes reverse incompatible changes which breaks the drivers and at worst apple specifically sabotages the drivers to keep people in the walled garden. This may be controversial but you also don’t have a right to merge in code to the kernel. If the maintainers don’t want rust cod…

> Agreed, supporting apple devices is going to be a maintenance nightmare as it goes against the wishes of apple. At best, apple involuntarily makes reverse incompatible changes which breaks the drivers and at worst apple specifically sabotages the drivers to keep people in the walled garden. Apple explicitly chose to provide a way to boot third-party operating systems when designing how the M-series SoC boots. Their…

> Apple explicitly chose to provide a way to boot third-party operating systems

And they explicitly chose against a UEFI interface like prior Macs, which would have actually enabled proper Linux support. Now you have poor people trying to reverse-engineer a Devicetree from scratch to get basic features to kinda work, emulating hardware features in software and working with no documentation from Apple. They "explicitly" chose to expose iBoot because otherwise you wouldn't be able to reinstall MacOS in a full data loss situation.

By comparison - reverse engineering an unsupported AMD or Intel CPU would at least give you some basis to work off of. You have UEFI as standard, ACPI tables provided by hardware, even CPU documentation and Open Source drivers to work off of most the time. Asahi shot themselves in the foot by trying to support hardware that doesn't support them back. You can argue that Apple was conspiring to help, but we have no actual evidence of that.

> Their SoC stuff dates in some components AFAIK back to the very first iPod SoCs in its design.

And none of those platforms ever got proper Linux support either. I love Linux as much as the next nerd, but it doesn't seem wild to suggest that Apple Silicon will never have feature-complete Linux support. And for many people, maybe that's okay!

Re: Resigning as Asahi Linux project lead

#534

Post by alienthrowaway »

ycombinatornews wrote: post #96
jazzyjackson wrote: post #12

God bless. Asahi introduced me to fedora/gnome, it feels rock solid on my m1 MacBook, and it's now my daily driver on a 2014 Intel Mac mini Wishing I had donated before, I'll sign up for opencollective now. I can only imagine the anticlimactic nature of releasing the emulation stack for gaming [0] and not seeing any increase in interest financially. One wonders what funding might have made it more worthwhile than sim…

OT, Have you had any issues with WiFi setup with this Mac Mini? I tried multiple distributions and most of them have troubles with detecting WiFi chip on 2014 mini.

Debian 11 & 12 detect the wifi on 2014 Mac Minis. I had to enable the nonfree sources, IIRC

Re: Resigning as Asahi Linux project lead

#535

Post by lenova »

ThatGuyRaion wrote: post #323
lenova wrote: post #140

This part of the post is being overlooked: Then 2024 happened. Last year was incredibly tumultuous for me due to personal reasons which I won’t go into detail about. Suffice it to say, I ended up traveling for most of the year, all the while having to handle various abusers and stalkers who harassed and attacked me and my family (and continue to do so). This is _not_ ok in any form, what the actual hell?

It's not okay but he's giving them ammunition by mentioning them and complaining about them. It proves that it's working. When I started getting harassed in 2022 over an ill advised post on a site, the only thing that stopped it was to sandbag everything and rethink how I interacted on the internet.

That's victim blaming, even when it's in reference to yourself.

Re: Resigning as Asahi Linux project lead

#536

Post by busterarm »

kmeisthax wrote: post #364
cornstalks wrote: post #229

Earlier quoted context omitted.

> Rust has a stability guarantee since 1.0 in 2015. Any backwards incompatibilities are explicitly opt-in through the edition system, or fixing a compiler bug. Unfortunately OP has a valid point regarding Rust's lack of commitment to backwards compatibility. Rust has a number of things that can break you that are not considered breaking changes. For example, implementing a trait (like Drop) on a type is a breaking ch…

Implementing (or removing) Drop on a type is a breaking change for that type's users , not the language as a whole. And only if you actually write a trait that depends on types directly implementing Drop[0]. Linux breaks internal compatibility far more often than people add or remove Drop implementations from types. There is no stability guarantee for anything other than user-mode ABI. [0] AFAIK there is code that ac…

> is a breaking change _for that type's users_, not the language as a whole.

And yet the operating mantra...the single policy that trumps all others in Linux kernel development...

is don't break user space.

Re: Resigning as Asahi Linux project lead

#537

Post by nromiun »

> For a long time, well after we had a stable release, people kept claiming Asahi Linux and Fedora Asahi Remix in particular were “alpha” and “unstable” and “not suitable for a daily driver” (despite thousands of users, myself included, daily driving it and even using it for servers).

Well, they were proved right.

Re: Resigning as Asahi Linux project lead

#538

Post by runjake »

xyzsparetimexyz wrote: post #231
thehias wrote: post #204

[flagged]

Regardless of whether hector is asahi Lina or not, the whole vtuber doing work that's important to a lot of people has a kinda off vibe and makes me a bit uncomfortable.

> Regardless of whether hector is asahi Lina or not

This isn't up for debate. There's tons of evidence out there, including the stream where his VTuber software failed briefly and he "doxxed" himself. It's not a fake. I was there watching, and rooting for him to succeed.

Rather than further clutter up this thread with the same links, yet again, I refer you to:

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

Re: Resigning as Asahi Linux project lead

#539

Post by vaxman »

uecker wrote: post #371
nindalf wrote: post #206

Earlier quoted context omitted.

If you watch that YouTube link, you'll see the same guy Ted Tso'o accusing the speaker of wanting to convert people to the "religion promulgated by Rust". I think he apologised for this flagrant comment, but this email shows he hasn't changed his behaviour in the slightest.

His email seems very reasonable to me (the thin-blue-line comment is a bit weird though). To me the problem are that some Rust people seem to expect that the Linux maintainers (that put in a tremendous amount of work) just have to go out of their way to help them achieve their goals - even if the maintainers are not themselves convinced about it and later have to carry the burden.

> "the thin-blue-line comment is a bit weird though"

In US, "thin blue line" is a colloquialism for police officers who typically wear blue and "toe the line." You should not be downvoted/shadowbanned/abused for your post, IMHO.

Post reply on HN