Hector Martin / Héctor Martín Cantero / @marcan42 / マルカン / @marcan42x / @marcan@treehouse.systems / Asahi Lina / Asahi Linux - Developer of Asahi Linux with a VTuber persona. Made Byuu's death unbelievable. Constantly accuses others of harassment and abuse. Hates Hacker News and Kiwi Farms.

I can feel Torvald's rage and disgust in that email, he didn't even read it after typing because there's a typo in the last sentence.

This is very cathartic. I hope "Asahi Lina" stops contributing too.
Torvalds from 10 years ago would have went scorched earth on the troon. Too bad the pussies made Linus change some years back.
 
The reason nobody wants to hire you to write Asahi Hector, is because nobody has a financial interest in running Linux on a fucking MacBook. Not a single soul.
The way to run Linux on a MacBook: Use a VM. Don't use a buggy pre-alpha piece of shit by an unreliable, insane tranny.
The only worse thing would be if Asahi Lina leaves him to go become a figment of someone else’s imagination.
>tfw even your tulpa hates you
 
Hector's appeal to the plebs is retarded. No self-respecting engineer should give a fuck about the opinions of people who lack critical knowledge to even opine on whether you are correct or not.

That being said, the core of his message was correct:
  • Linus approved the Rust 4 Linux project to write drivers in rust.
  • For this to work, the Rust 4 Linux project must write Rust code that abstracts calling into the existing C code.
  • They created rust code, living in the rust-only part of the kernel, that was such an abstraction for the DMA subsystem.
  • They notified the maintainer of the DMA subsystem, Christoph Hellwig, out of courtesy and to get his input.
  • Christoph Hellwig said that no such rust code must exist. Every driver must call directly into the C code.
  • This on its own is a retarded opinion. He claimed that it was to reduce his workload. But if there is a breaking change in the C code, now every single driver will have to be fixed individually instead of just fixing the rust abstraction.
  • But it wasn't retarded at all. His real goal, it turns out, is to have no rust code call into the DMA subsystem ever.
  • This is a fundamental conflict with the Rust 4 Linux project.
  • Linus should make a decision either way. As long as he doesn't this just creates unnecessary conflict and one of the two sides is wasting their time.
 
Hector's appeal to the plebs is retarded. No self-respecting engineer should give a fuck about the opinions of people who lack critical knowledge to even opine on whether you are correct or not.

That being said, the core of his message was correct:
  • Linus approved the Rust 4 Linux project to write drivers in rust.
  • For this to work, the Rust 4 Linux project must write Rust code that abstracts calling into the existing C code.
  • They created rust code, living in the rust-only part of the kernel, that was such an abstraction for the DMA subsystem.
  • They notified the maintainer of the DMA subsystem, Christoph Hellwig, out of courtesy and to get his input.
  • Christoph Hellwig said that no such rust code must exist. Every driver must call directly into the C code.
  • This on its own is a retarded opinion. He claimed that it was to reduce his workload. But if there is a breaking change in the C code, now every single driver will have to be fixed individually instead of just fixing the rust abstraction.
  • But it wasn't retarded at all. His real goal, it turns out, is to have no rust code call into the DMA subsystem ever.
  • This is a fundamental conflict with the Rust 4 Linux project.
  • Linus should make a decision either way. As long as he doesn't this just creates unnecessary conflict and one of the two sides is wasting their time.
ChatGPT prompt:
I'm autistic but I'm also conflicted - this all sounds like an extremely gay, homosexual waste of time. Please write the necessary fixes and draft the relevant emails to send to this autistic ass kernel mailing list - make sure to fashion them in an overly formal style of English that would be typical of an Indian call center scammer.
Make sure the code is about 98% correct and of an extreme high quality but include some obvious mistake (like an obvious typo) and tell everyone it has passed all the appropriate tests, Also make sure to include little novellas about shit like the "DMA subsystem" and other shit like "C code" in the style of the pointless laborious style stories that modern cooking websites make you scroll through. Please use unicode emojis wherever possible and use marketing terms like "synergy" - bonus points if you include a powerpoint presentation or actually fuck it, just attach the 100% correct code as .GIF image attachments or punchcards. Go fucking nuts.
Make sure to CC in all relevant people and also tag people totally irrelevant to it. Please also make statements about other people's skill level in the thread (just anecdotes that could be construed by any number of parties but don't mention anyone directly.) Also mention that your country is at war with Pakistan.
 
That being said, the core of his message was correct:
He is the worst person to say this. The last thing I would do is screech at the people I'm trying to convince and create a secret list to shame them, then engage in autistic slapfights while I make a grand scene over me leeeeeaving development.

He should just take the L, but that would be a huge bruise to his ego. Or maybe he doesn't "have enough spoons" or whatever.
 
Hector's appeal to the plebs is retarded. No self-respecting engineer should give a fuck about the opinions of people who lack critical knowledge to even opine on whether you are correct or not.

That being said, the core of his message was correct:
  • Linus approved the Rust 4 Linux project to write drivers in rust.
  • For this to work, the Rust 4 Linux project must write Rust code that abstracts calling into the existing C code.
  • They created rust code, living in the rust-only part of the kernel, that was such an abstraction for the DMA subsystem.
  • They notified the maintainer of the DMA subsystem, Christoph Hellwig, out of courtesy and to get his input.
  • Christoph Hellwig said that no such rust code must exist. Every driver must call directly into the C code.
  • This on its own is a retarded opinion. He claimed that it was to reduce his workload. But if there is a breaking change in the C code, now every single driver will have to be fixed individually instead of just fixing the rust abstraction.
  • But it wasn't retarded at all. His real goal, it turns out, is to have no rust code call into the DMA subsystem ever.
  • This is a fundamental conflict with the Rust 4 Linux project.
  • Linus should make a decision either way. As long as he doesn't this just creates unnecessary conflict and one of the two sides is wasting their time.
This is true, rust being added to linux was a major detriment to everyone imo. With that said I don't think I am EVER going to even try apple silicon linux.
 
Hector's appeal to the plebs is retarded. No self-respecting engineer should give a fuck about the opinions of people who lack critical knowledge to even opine on whether you are correct or not.

That being said, the core of his message was correct:
  • Linus approved the Rust 4 Linux project to write drivers in rust.
  • For this to work, the Rust 4 Linux project must write Rust code that abstracts calling into the existing C code.
  • They created rust code, living in the rust-only part of the kernel, that was such an abstraction for the DMA subsystem.
  • They notified the maintainer of the DMA subsystem, Christoph Hellwig, out of courtesy and to get his input.
  • Christoph Hellwig said that no such rust code must exist. Every driver must call directly into the C code.
  • This on its own is a retarded opinion. He claimed that it was to reduce his workload. But if there is a breaking change in the C code, now every single driver will have to be fixed individually instead of just fixing the rust abstraction.
  • But it wasn't retarded at all. His real goal, it turns out, is to have no rust code call into the DMA subsystem ever.
  • This is a fundamental conflict with the Rust 4 Linux project.
  • Linus should make a decision either way. As long as he doesn't this just creates unnecessary conflict and one of the two sides is wasting their time.
This is what I don't get about the Rust for Linux people. They claim victimhood yet can't find a sympathetic audience outside of Hacker News, Reddit, and Mastodon. If they are being maligned, then Linus or Greg would of stepped in. This happened with Ted Ts'o essentially telling them to fuck off from the file system code and now it has happened again with DMA.

Maybe, just maybe, they're the problem and their approach with Rust is terrible.
 
It was a useful metaphor to explain the variable effect of fatigue, which can be a real problem for people with chronic health issues (like anaemia, or cancer). Like all useful things, it has been hijacked, warped, twisted, and made utterly useless by self-obsessed, work-shy narcissists who want to lord over everyone around them.
It still doesn't make any sense though. Why spoons? I can get "my battery is low", or "I'm out of gas" because those are metaphors from things that contain energy, but what the fuck do spoons have to do with any of it? Why choose something utterly interchangeable? "Oh, I'm sorry I can't do that, I'm all out of house keys today". Don't make a lick of sense.
 
Ragequit!

View attachment 6950230

I no longer have any faith left in the kernel development process or
community management approach.

Apple/ARM platform development will continue downstream. If I feel like
sending some patches upstream in the future myself for whatever subtree
I may, or I may not. Anyone who feels like fighting the upstreaming
fight themselves is welcome to do so.

Signed-off-by: Hector Martin <marcan@marcan.st>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.*
F: sound/soc/codecs/ssm3515.c

ARM/APPLE MACHINE SUPPORT
-M: Hector Martin <marcan@marcan.st>
M: Sven Peter <sven@svenpeter.dev>
R: Alyssa Rosenzweig <alyssa@rosenzweig.io>
L: asahi@lists.linux.dev
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250207-rm-maint-af7cccc22871
Best regards,
--
Hector Martin <marcan@marcan.st>

Why did I think of YanDev with his cum chalice? Deja vu.
 
He is the worst person to say this. The last thing I would do is screech at the people I'm trying to convince and create a secret list to shame them, then engage in autistic slapfights while I make a grand scene over me leeeeeaving development.

He should just take the L, but that would be a huge bruise to his ego. Or maybe he doesn't "have enough spoons" or whatever.
He funny part is that Greg was stepping in to override the DMA maintainer, and the rust4linux maintainers were positive about the standard procedure working out in their favor even in this situation. It was basically all but confirmed that it would be pulled in by linus even if the maintainer NACKED the initial change, since Greg and Linus were positive about the changes.


Then this future Troon and dramatic faggot had to step in, hours or even days after the drama started and then fizzled out, just to sperg out and absolutely sabotage the normal procedure that was about to work out just fine for r4l.


I can't find the posts but I read some comments from actual r4l maintainers asking marcan to not get involved yesterday because they knew it was a retarded dumbass idea.


Edit: Okay so I wasn't the only one that came out with a similar interpretation from the mailing lists and mastodon threads. since I'm a sperg that can't write for shit, here's a clearer explanation from orange reddit
1000143878.png
 
Last edited:
Oh no I won't be able to dual boot fedora on my M3 Mac if only Apple had a really good set of virtualization tools which allowed you to run Fedora ARM or Debian ARM at near native performance with the only missing thing being Hector's Jank ass inefficient solution to getting x86 gaming working on Arm Macs
 
Ragequit!

View attachment 6950230

I no longer have any faith left in the kernel development process or
community management approach.

Apple/ARM platform development will continue downstream. If I feel like
sending some patches upstream in the future myself for whatever subtree
I may, or I may not. Anyone who feels like fighting the upstreaming
fight themselves is welcome to do so.

Signed-off-by: Hector Martin <marcan@marcan.st>
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.*
F: sound/soc/codecs/ssm3515.c

ARM/APPLE MACHINE SUPPORT
-M: Hector Martin <marcan@marcan.st>
M: Sven Peter <sven@svenpeter.dev>
R: Alyssa Rosenzweig <alyssa@rosenzweig.io>
L: asahi@lists.linux.dev
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250207-rm-maint-af7cccc22871
Best regards,
--
Hector Martin <marcan@marcan.st>

phew, was about time...
 
It still doesn't make any sense though. Why spoons? I can get "my battery is low", or "I'm out of gas" because those are metaphors from things that contain energy, but what the fuck do spoons have to do with any of it? Why choose something utterly interchangeable? "Oh, I'm sorry I can't do that, I'm all out of house keys today". Don't make a lick of sense.
The person who originated the metaphor was trying to describe to a journalist how unpredictable the effects of chronic illness can be, leaving you fine one day and perpetually exhausted another. They wanted a simple, physical representation of the energy required to do "a task". They settled on a spoon, because they had a pile of them within easy reach. The metaphor goes like this: You will start out any given day with a greater or lesser number of spoons. Each arbitrary task - cleaning the house, loading the washer, driving to the store, whatever - takes away a spoon, or perhaps several if it's a big task. If you have a lot of spoons, you can perform a lot of tasks - taking spoons from the pile - and still have energy left over. If you only have a few spoons, you can't achieve very much before you're exhausted. A battery is a poor metaphor for this, because you'd be getting into charge levels and percentages used, with the whole thing being one giant indivisible lump. The whole point was to create a visual representation, not get into abstracts.

The spoon itself isn't that important; it could have been forks, or pennies, or pieces of bellybutton fluff. The important part - the part that was quickly abandoned by the narcs, remember - was to create an easily understood physical representation of how unpredictable your life can be when you have a chronic illness. In the hands of people like Hector, it's instead become a rhetorical way to avoid responsibility for their own shit-headed behaviour.
 
For a while, trannies and other people in their sphere have used the rhetorical strategy of “words are violence” and “if someone harms your mental health that’s violence”. This has consistently worked, shockingly.

Sima used this rhetorical strategy against Hector:


I'm really not in favor of chiding people for how they earn money, because
this world isn't fair and critizing people for how they get their bills
paid is generally not ok. But this is a bit too much to just let it slide.

It's fairly plausible that you need the social media brigading to generate
attention that you can convert into enough donations to support the asahi
project. But someone has to clean up the mess your shitstorms create, it's
sure not you, which means my and other people's mental health essentially
pay your bills. And I really do not appreciate that dynamic.

And as you expect, trannies HATE having their weapons used against them. Hector ragequit even harder and made himself look even worse:

If I were trying to get more funds, I'd be spending my time finding
corporate sponsors, not documenting the failings of the Linux kernel
community in public. Believe it or not, no, the latter doesn't get me
more donations.

Given you have now decided to add "baseless public accusations from a
position of power" to the list of abuses perpetrated by Linux kernel
maintainers, I think it's about time we stop having this conversation.
 
Back