Asahi Linux Lead Developer Hector Martin Steps Down As Upstream Apple Silicon Maintainer

[lefantome@programming.dev]

RISC-V is the “new” CPU architecture

[robertomorrison@lemmy.world]

Even “smart people” have resource/time limitations. Learning rust to an extent that will work on that level is not the same as learning C.

[dreadbeef@lemmy.dbzer0.com]

The rust people said they'd take ownership of the work for the bindings. What's the issue?

[industrystandard@lemmy.world]

Does the kernel not need a lot of memory unsafe Rust code? There is a way to bypass the safety nets and I heard that for stuff like kernel development that is necessity.

[integrate777@discuss.online]

Hector posting it to social media, and by his own admission, to shame the C devs, is pretty hostile and bad faith too.

[andrewd18@midwest.social]

This kind of stuff happens in big companies too, but you don't see it because it's not in a public mailing list. One of my teams had a developer who stood on tables to yell until his opinion was accepted, and one time when another developer wouldn't back down, he threw a chair at them. That angry developer worked there for another 7 years until retirement, while many smart team members around him quit rather than continue dealing with him.

[penquin@lemm.ee]

. I'd beat the shit out of the mother fucker. I get that he's a smart developer, but you don't fucking throw a chair at me, bitch.

[merthyr1831@lemmy.ml]

Linus needs to step back again. He's a liability to the kernel's long term sustainability.

[ziltoid1991@lemmy.world]

1. Dumb culture wars around programming languages.
2. It a lot different from C. In C, you have Typeidentifier variable;, in Rust you have let mut variable : Typeidentifier;, and it's just the tip of the iceberg.
3. Some of its safety features (including RAII - a favorite feature of marcan) are both detrimental to the performance and hard or impossible to opt out from.

[omega_jimes@lemmy.ca]

There's a lot of issues with Rust taking more and more of the kernel. I'd like to see the whole kernel transitioned to Rust, but the project can't stand still for that amount of time. Unless someone is willing to take that on, I think it's better that Rust "stay in it's lane", as gross as that sounds.

[sitd@lemy.lol]

nope, Tim Cook should step down

[m1ch431@lemmy.ml]

Social media is virtual town hall and a place for many to vent and deal with their emotions - not everybody is perfect and uses the internet the way you approve of. It's truly no different in essence than the LKML or other public-facing communication platforms - it just has more voices and more free engagement. We can be big people who express ourselves any way we'd like as long as we respect others the way we'd like to be respected.

I don't advocate for shaming because I wouldn't want it done to me, but what transpired is not "bad faith", and it's questionably hostile because Hector clearly wavered in their approach. They are under a lot of stress and are obviously motivated by the feelings of the other R4L maintainers and their issues - their good faith and empathy is plain to see. They are very upset that others are being disrespected and that their efforts are likened to a "cancer".

Did Hector disrespect the maintainer in question? Did Hector call people to action in order to shame the maintainer in question? Their initial intention did matter, of course, and I was not able to read the drama in question on social media because it appears to be removed. Hector certainly wanted the maintainer removed, which I don't personally agree is ideal or fair, but it's not their decision and it's not social media's decision.

On the flip-side in this instance, I similarly see somebody who brings up valid issues with splitting the codebase accompanied by a lot of emotions spilling out (like seeing Rust as a cancer, and essentially vowing to stop it from spreading in the codebase further), but I personally fail to see how that is their problem if the code isn't going to involve them. It's up to the Linus and the larger community to discuss the form in which Rust will take in the Linux kernel. Clearly a discussion that could be had with Hector, but there is a lot of hostility towards public focus coming from Linus, and he effectively shut the discussion down.

[m1ch431@lemmy.ml]

Yes, from my understanding as an outsider and layman, of course. From my perspective, the observation and insights developed from the R4L project will make Linux much stronger project overall moving forwards.