Asahi Linux lead developer Hector Martin resigns from Linux kernel

Post by adrienne » Mon, Feb 10, 2025, 12:24 AM UTC

eqvinox wrote: post #920

adrienne wrote: post #915

Earlier quoted context omitted.

I am on the moderation team at Treehouse. Marcan has not violated any of our community guidelines and he categorically was not suspended from our Fediverse instance. He chose to delete his own account.

I can reproduce the bug: 1. go to https://social.treehouse.systems/explore 2. type @marcan in the search box 3. select "go to profile" from suggestions Feels like a problem with the dynamic/partial JS content loading. (Apologies for the confusion, there's no indication that made me suspect a bug... and I hadn't at that point seen anything about him deleting his own account yet.)

Post by starspangled » Mon, Feb 10, 2025, 2:42 AM UTC

Locutus_ wrote: post #810

starspangled wrote: post #491

Earlier quoted context omitted.

Yeah m68k is still around too and it has more than a decade on alpha. People use and maintain them and they have very little impact outside arch/ nowadays so they're on the happy side of cost/benefit I guess.

M68k has the advantage that it has a fairly typical memory model. Alpha's memory model has problems with providing atomic access to single bytes, which i'd imagine in a kernel is a bit annoying :-) And then there's just the social aspect, m68k was used in the Amiga/Atari/Mac/QL/x68k, so there is a whole generation of us m68k fans who are willing to keep it alive. Alpha has it's fans (me included!), but it's not exact…

Post by samus » Mon, Feb 10, 2025, 7:35 AM UTC

arp242 wrote: post #950

samus wrote: post #578

Earlier quoted context omitted.

Which sounds inefficient and exactly the sort of problem that doesn't happen with a Github issue/PR.

> exactly the sort of problem that doesn't happen with a Github issue/PR What? PRs or issues being forgotten happens all the time, especially for large projects.

Post by ranguna » Mon, Feb 10, 2025, 9:52 AM UTC

vednig wrote: post #592

ranguna wrote: post #564

Earlier quoted context omitted.

> the fact that rust is highly compute intensive language care to elaborate on that?

rust utilizes various methods at compile time which significantly increases compute, such as compiler is optimised for memory safety, which causes it do a lot of tasks and changes at compile time unlike C and inturn during execution to ensure ms, which could easily be avoided, it is good for overflow situations but in terms of compute required in exchange for the program is simply(currently) not at the level that wou…

Post by account42 » Mon, Feb 10, 2025, 12:16 PM UTC

soraminazuki wrote: post #356

e40 wrote: post #284

Earlier quoted context omitted.

> Threatening a social media campaign to out people is completely toxic behaviour. This is a long-term contributor who is perhaps a bit abrasive, not Jimmy fucking Saville. I'm no where near in the loop on this, but that sounds incredibly toxic. Are there some good links to summarize this? EDIT: OK, these are fully enough to allow me to understand the issue. Marcan: https://lore.kernel.org/rust-for-linux/208e1fc3-cfc…

https://archive.is/rESxe This is a recurring pattern I see with drama in some open source communities, where people measure others using yardsticks they themselves don't live up to. People can't post stuff like this while accusing everyone in the vicinity except themselves of bad behavior. Choose one.