Asahi Linux Lead Developer Hector Martin Steps Down As Upstream Apple Silicon Maintainer
-
[email protected]replied to [email protected] last edited by
I always thought kernel devs were smart people. I'm kind of shocked learning a new language is this big of a barrier to them.
-
[email protected]replied to [email protected] last edited by
They kind of already do. The C used by the kernel team isn't the exact same as what everyone else uses. Mainly because of the tooling they've built around it. I can't remember specifics, but the tooling in place really helps out in that department.
Also, "memory safe C" is already a proposal for the C lang project.
-
[email protected]replied to [email protected] last edited by
Not a fork of course but there is Redox
-
[email protected]replied to [email protected] last edited by
No. The kernel does not care about X11 vs Wayland. Or rather, both X11 and Wayland use KM| ( Kernel Mode Setting ) and DRM ( Direct Rendering ) these days. That is, both X11 and Wayland call on the same kernel features.
-
[email protected]replied to [email protected] last edited by
RISC-V is the “new” CPU architecture
-
[email protected]replied to [email protected] last edited by
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.
-
[email protected]replied to [email protected] last edited by
The rust people said they'd take ownership of the work for the bindings. What's the issue?
-
[email protected]replied to [email protected] last edited by
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.
-
[email protected]replied to [email protected] last edited by
Hector posting it to social media, and by his own admission, to shame the C devs, is pretty hostile and bad faith too.
-
[email protected]replied to [email protected] last edited by
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.
-
[email protected]replied to [email protected] last edited by
. 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.
-
[email protected]replied to [email protected] last edited by
Linus needs to step back again. He's a liability to the kernel's long term sustainability.
-
[email protected]replied to [email protected] last edited by
- Dumb culture wars around programming languages.
- It a lot different from C. In C, you have
Typeidentifier variable;
, in Rust you havelet mut variable : Typeidentifier;
, and it's just the tip of the iceberg. - 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.
-
[email protected]replied to [email protected] last edited by
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.
-
[email protected]replied to [email protected] last edited by
nope, Tim Cook should step down