This makes sense, he either had to accept that there would be a rust binding in that tree he was maintaining, where he didn’t want it, or withdraw from that position. After the developments in the story so far, there was no real other outcome possible.
I find it of note that hes only stepping down from the DMA mapping and still maintains other parts, so its really just about rust.
Good. This dev has explicitly said that he has non-technical reservations, and that he’ll abuse his position to get his view pushed through.
I hope they can keep themselves from doing the same for the rest of the systems they’re maintaining.
Bye 👋
It’s probably for the best for everyone involved.
The comments on phoronix are written by moronix. Good grief, it’s like watching idiots brawl in the mud. But I can’t look away for some reason.
@toothbrush so much drama and fragile prides hurt, are they finally gonna get back to coding?
In my opinion the other dev involved stepping down was inevitable, I read their recent blog posts and it seems like more burnout and this being the final straw.
Though the constant resistance from people like Hellwig were part of the reason for that burn out, though not the only reason.
to be fair, you can ask the same of many rust devs themselves
@refalo oh I wasn’t picking sides, I meant that for everyone involved. Less fighting and more coding; most linux users don’t really care about language used as long as it works, and fast if it’s possible
Rust is a psyop
Rust has its uses, it certainly has its place in the world of languages. I think if you are making a new low level project, rust is a good pick.
The Rust4Linux project was always fundamentally going to create disagreements and strife. Lots of angry headbutting was to be expected. It happening in such a public way, with sizeable collateral damage, was not.
