💪 Tough Guys 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.

Wyróżnienie
Screenshot_20241125-215207_Reddit.png
Weren't those two faggots supposed to be getting married? I wonder what put a stop to the happy day...
Screenshot_20241125-215539_Chrome.png
Apparently true love has its price. $10,000 to be exact. What a shame they need better pay pigs.
 
REEEEEEEEEEEEEEEEEEEEEEE! powiedział(a):
Wyświetl załącznik 6687709
Weren't those two faggots supposed to be getting married? I wonder what put a stop to the happy day...
Wyświetl załącznik 6687717
Apparently true love has its price. $10,000 to be exact. What a shame they need better pay pigs.
Kliknij, aby rozwinąć...
I maintain my personal theory that it's money earmarked to do marriage fraud (Hector goes to Europe for a week, gay marry, and go back to Japan where foreign homosexual marriages are recognized for diplomatic reasons) and pay for the Cyan guy to move to Tokyo under a family visa.

I may have forgotten about it but how much do we know about the Cyan guy? I know he's Chinese but that's about it.
 
Hector/Lina are back in the news because of drama surrounding the encroachment of Rust into the Linux kernel. For the non-technical thread readers, RAII (Resource Acquistion is Initialization) is a pattern common in languages like C++ and Rust. The tl;dr is that this is an idiom where saying something exists also allocates the resources for it (memory in this case) and saying it should stop existing frees those resources. This is extremely common and good in regular userspace applications because it simplifies the management of resources and makes it easier to avoid leaking memory.

However in the kernel, explicitly deallocating shit the second it stops being used is problematic due to the fact the kernel is running the entire computer and so taking the time to allocate/deallocate whenever composite data types move in and out of scope can interrupt the actual important shit the kernel is doing (like scheduling processes, handling network traffic, etc) and there are certain conditions where code using RAII incorrectly can hang the entire program.

As such, the Linux kernel jannies are not interested in having this in the kernel. They'd prefer to stick to more boring memory management patterns. What is Hector/Lina's response? "RAII is technically good and correct and gives me the dopamine when I see my objects dtoring. Also I'm a heckin valid woman so fuck you kernelchuds"

The drama has reached the point where rustrannies have tried rewriting some of the surrounding C code for the Direct Rendering Manager to support their mental illness which then resulted in an immediate bitchslap from the maintainers followed by several of the rustrannies 'quitting.'
 
Fcret powiedział(a):
Hector/Lina are back in the news because of drama surrounding the encroachment of Rust into the Linux kernel. For the non-technical thread readers, RAII (Resource Acquistion is Initialization) is a pattern common in languages like C++ and Rust. The tl;dr is that this is an idiom where saying something exists also allocates the resources for it (memory in this case) and saying it should stop existing frees those resources. This is extremely common and good in regular userspace applications because it simplifies the management of resources and makes it easier to avoid leaking memory.

However in the kernel, explicitly deallocating shit the second it stops being used is problematic due to the fact the kernel is running the entire computer and so taking the time to allocate/deallocate whenever composite data types move in and out of scope can interrupt the actual important shit the kernel is doing (like scheduling processes, handling network traffic, etc) and there are certain conditions where code using RAII incorrectly can hang the entire program.

As such, the Linux kernel jannies are not interested in having this in the kernel. They'd prefer to stick to more boring memory management patterns. What is Hector/Lina's response? "RAII is technically good and correct and gives me the dopamine when I see my objects dtoring. Also I'm a heckin valid woman so fuck you kernelchuds"

The drama has reached the point where rustrannies have tried rewriting some of the surrounding C code for the Direct Rendering Manager to support their mental illness which then resulted in an immediate bitchslap from the maintainers followed by several of the rustrannies 'quitting.'
Kliknij, aby rozwinąć...
As a linux user this just pisses me off. For fucks sake all i want is a goddamn kernel that works, and a goddamn operating system that works. Windows got absolutely thrown in the shitter and enshittifed because of corporate greed, and now linux is getting ruined because the trannies think their opinion is objectivly right because they got their dicks chopped off...

Also RAII isn't all that bad as a memory management system, when used correctly. Here, it is not used correctly.
Diesel Boogaloo powiedział(a):
Only the ones that use voice filters.
Oh wait, you meant in general, not only in the voice aspect? Then yes, all of them.
Kliknij, aby rozwinąć...
Im pretty sure i read earlier how that faggot managed to overwhelm a M SERIES macbook, a fucking M series with the sheer number of voice filters. Using a lot of sound filters doesn't make you competent, infact it shows you have no idea what you are doing, and as far as i know this boils down to him pitching his voice up by a really large amount which you need like.... 1 filter for. You don't need a lot of voice filters, it's not necessery. Just as having a program that is hundreds of lines of code long doesn't automatically make you a superior programmer, infact, if your code is 500 lines for something that can be done in 400, then all you are telling people is that you are shit at optimizing code and not as good/experienced as you tought you were. Bascially hector is not only a faggot, but also a faggot vtuber, and is also kinda bad at being a vtuber and emulating a catgirl or whatever.

"A idiot basks at complexity, a genius admires simplicity" - Terry. A. Davis.
 
Fcret powiedział(a):
Hector/Lina are back in the news because of drama surrounding the encroachment of Rust into the Linux kernel. For the non-technical thread readers, RAII (Resource Acquistion is Initialization) is a pattern common in languages like C++ and Rust. The tl;dr is that this is an idiom where saying something exists also allocates the resources for it (memory in this case) and saying it should stop existing frees those resources. This is extremely common and good in regular userspace applications because it simplifies the management of resources and makes it easier to avoid leaking memory.
Kliknij, aby rozwinąć...
lol ref counting is used everywhere in the kernel

linux is 99% drivers who even cares about changing the core stuff, it's not where the value is anymore. writing a driver is p easy at this point anyway, and if the rust fags made that nicer it'd be 100x more valuable vs trying to jam it into place it is a poor fit (But is on brand for faggots amirite)
 
Looks like the post about Hector getting married and the community happening post highlighting it were lost while the site went down.
 
Fcret powiedział(a):
As such, the Linux kernel jannies are not interested in having this in the kernel. They'd prefer to stick to more boring memory management patterns. What is Hector/Lina's response? "RAII is technically good and correct and gives me the dopamine when I see my objects dtoring. Also I'm a heckin valid woman so fuck you kernelchuds"
Kliknij, aby rozwinąć...
Does anyone actually even care what this deranged tranny "thinks" about anything? Why?
 
AnOminous powiedział(a):
Does anyone actually even care what this deranged tranny "thinks" about anything? Why?
Kliknij, aby rozwinąć...
Hector has a lot of dickriders in the tech scene actually. It's not uncommon for them to come out of the woodwork if you don't suck xir dick on hackernews or in certain parts of youtube.
 
Fcret powiedział(a):
Hector/Lina are back in the news because of drama surrounding the encroachment of Rust into the Linux kernel. For the non-technical thread readers, RAII (Resource Acquistion is Initialization) is a pattern common in languages like C++ and Rust. The tl;dr is that this is an idiom where saying something exists also allocates the resources for it (memory in this case) and saying it should stop existing frees those resources. This is extremely common and good in regular userspace applications because it simplifies the management of resources and makes it easier to avoid leaking memory.

However in the kernel, explicitly deallocating shit the second it stops being used is problematic due to the fact the kernel is running the entire computer and so taking the time to allocate/deallocate whenever composite data types move in and out of scope can interrupt the actual important shit the kernel is doing (like scheduling processes, handling network traffic, etc) and there are certain conditions where code using RAII incorrectly can hang the entire program.

As such, the Linux kernel jannies are not interested in having this in the kernel. They'd prefer to stick to more boring memory management patterns. What is Hector/Lina's response? "RAII is technically good and correct and gives me the dopamine when I see my objects dtoring. Also I'm a heckin valid woman so fuck you kernelchuds"

The drama has reached the point where rustrannies have tried rewriting some of the surrounding C code for the Direct Rendering Manager to support their mental illness which then resulted in an immediate bitchslap from the maintainers followed by several of the rustrannies 'quitting.'
Kliknij, aby rozwinąć...
That's not a very good article. RAII just means automatically running destructor code when something goes out of scope. The advantage to this over the C way of doing it manually is that sloppy programmers can't forget to do this.

The article then spergs about whether deallocation is a good thing to do at all, which is a different matter. Deallocation is usually very cheap, I highly doubt it's going to be the bottleneck in kernel code - and if it is, there's tricks you can do to mitigate this.

Much as I dislike Hector, he's not wrong here.
 
Wyróżnienie
Musisz się zalogować lub zarejestrować, aby odpowiedzieć.
Wstecz
Top Na dole