Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
I like LMDE, runs bulletproof in a VM. Put it in a physical machine I have for it and cinnamon crashes every few hours goes to fallback mode. Tried it another physical machine, same thing. Can't just start it in fallback mode of course because why in the soygoy would you want to do that?? Guess I better grep the logs, check the repos, switch to unsupported whatever, patch more stuff to break other stuff not broken yet and wait for some registered debian troon diddlers to upload some NSA backdoor code to fix it. (just give me my tophat you LMDE niggers).
have you tried Mint actual, the one based on Ubuntu? LMDE is technically a backup in case Ubuntu gets so horrible Mint has to rebase off Debian itself, but it's a little more bare bones compared to Mint.
 
have you tried Mint actual, the one based on Ubuntu? LMDE is technically a backup in case Ubuntu gets so horrible Mint has to rebase off Debian itself, but it's a little more bare bones compared to Mint.

Been about 5 years I remember liking it even less and probably didn't use it long enough to have issues. Parrot is my favorite Debian by far I just needed a more normie desktop ideally avoiding anything Ubuntu. However Ubuntu's diddler brigade has seeped into Debian and vice versa now so less of an issue I guess at this point. Debian plain with MATE was good but pain in the ass out of the box and MATE was based on bringing back the dodo only to become the dodo now. LMDE/Debian got everything I need out of the box, other than the gui crashing more than windows98.
 
Put it in a physical machine I have for it and cinnamon crashes every few hours goes to fallback mode. Tried it another physical machine, same thing. Can't just start it in fallback mode of course because why in the soygoy would you want to do that??
To be fair I have so far never had this happen so I think you just suck
 
Parrot is my favorite Debian
Luckily for you Parrot has a "home" installation now, which should ship with your typical suite of office + convenience stuff + pretty sure they also have vscodium in their main repos if you're into that. And it looks like they recently updated to use Deb 13. If you like it, use it! (Kali is for larping jeets, parrot is the TRVE chud's choice).
 
Luckily for you Parrot has a "home" installation now, which should ship with your typical suite of office + convenience stuff + pretty sure they also have vscodium in their main repos if you're into that. And it looks like they recently updated to use Deb 13. If you like it, use it! (Kali is for larping jeets, parrot is the TRVE chud's choice).

They've had home since 5.x and you could also build minimal from scratch but they dropped that in favor of full debian conversion script. Home is ok but whistles and bells if you are not using it for the main sec features. The 5.x branch was killer and still use it, 6.0 a mess, 6.4 is good now for new hardware but will be the last 6.x. I don't know what the new path is for 7.x could be rough again. lol@Kali jeets its true jeets hate parrot one more thing to learn before you can scam.
 
Driving by to say that Rust is a low-tier shit language for anyone who doesn't know how to code well and everyone who uses it is/supports troonery.
 

The (successful) end of the kernel Rust experiment​

The topic of the Rust experiment was just discussed at the annual Maintainers Summit. The consensus among the assembled developers is that Rust in the kernel is no longer experimental — it is now a core part of the kernel and is here to stay. So the "experimental" tag will be coming off. Congratulations are in order for all of the Rust for Linux team.
(Stay tuned for details in our Maintainers Summit coverage.)

Is this the official Rust seething thread?
 
they can put rust into the kernel and I can carve it back out.
i don't think I currently use anything on my system that rust touches.

I'm an autist that compiles my own kernel (at least sometimes). and I've never even enabled the rust parts of the codebase for a build. You have to do it with an environment variable iirc.
 
Ok, but why would you do that? Ideological reasons? Or practical?
If I put my hate for most of the rust community aside, it's practical reasons, I prefer to work with a single language per project unless I am dealing with a language like python and need custom native dependencies. I would rather not need 2 compilers for a project, plus debugging rust even with its tools is painful. Especially when you need to cross the border in applications that mix c++ and rust.

I will put this into a separate post, but while rust does have its benefits, its community (even if you put all the politics aside) uses it like its the gods tongue and expects the compiler to solve all their bad code. The llvm toolchain might be amazing at optimizing code but even it has its limits and rust being a custom language breaks many of the optimization pipelines that would fix some of the more egregious faults. Plus on top of that the compiler/language itself isn't mature yet so it can change underneath you causing lots of undefined behavior.

TLDR: crazy coders think that the rust compiler will magically fix thier yandere-dev level code. While also relying on a custom language that hasn't even reached maturity yet.
 
I will put this into a separate post, but while rust does have its benefits, its community (even if you put all the politics aside) uses it like its the gods tongue and expects the compiler to solve all their bad code. The llvm toolchain might be amazing at optimizing code but even it has its limits and rust being a custom language breaks many of the optimization pipelines that would fix some of the more egregious faults. Plus on top of that the compiler/language itself isn't mature yet so it can change underneath you causing lots of undefined behavior.

TLDR: crazy coders think that the rust compiler will magically fix thier yandere-dev level code. While also relying on a custom language that hasn't even reached maturity yet.
Are you a woman? This is a very feminine ingroup-outgroup way of thinking. I don't even know what the "Rust community" is, what they think, or who the members are. If you have to use an angle grinder do you first check if there are any leftists in the angle grinder community to know if you're allowed to use it?
 
rust-consent.jpeg
 
Are you a woman? This is a very feminine ingroup-outgroup way of thinking. I don't even know what the "Rust community" is, what they think, or who the members are. If you have to use an angle grinder do you first check if there are any leftists in the angle grinder community to know if you're allowed to use it?
No, I just prefer gatekeeping, especially in current year, because the programming space has changed from feature creep to rust creep. I wish I didn't need to care about if something is written in rust, but with many major projects like the coreutils rewrite causing massive failures, I instinctually don't trust anything written in rust.
 
Last edited:
I like LMDE, runs bulletproof in a VM. Put it in a physical machine I have for it and cinnamon crashes every few hours goes to fallback mode. Tried it another physical machine, same thing. Can't just start it in fallback mode of course because why in the soygoy would you want to do that?? Guess I better grep the logs, check the repos, switch to unsupported whatever, patch more stuff to break other stuff not broken yet and wait for some registered debian troon diddlers to upload some NSA backdoor code to fix it. (just give me my tophat you LMDE niggers).
Distros love to be finnicky like that. I tried Artix with Calamares in a VM, worked flawlessly. Wanted to install it on a ThinkPad T420, would refuse to load the graphics driver or some other display issue at the very beginning of booting. Plain old Arch with archinstall? VM and the same machine, all flawless.

It's one of the longest running issues of Linux: odd behavior depending on the distro and hardware configuration, and I can say with certainty that anyone saying that "this is no longer an issue with Linux" whenever confronted with that fact is full of shit because it still is a dice roll whether or not this specific distro with this specific kernel on this specific machine will work or not. There's always a more lower level, long standing issue with Linux that everyone refuses to pay attention to while constantly glorifying surface level victories like "you can game on Linux". Couldn't care less if the foundation rot is constantly left unchecked. Fix your shit, an OS is meant to be good code first and foremost.
 
I don't even know what the "Rust community" is

a4b1fb49f9d6e0cd41d28b1ca035a23b.jpeg

It's one of the longest running issues of Linux: odd behavior depending on the distro and hardware configuration, and I can say with certainty that anyone saying that "this is no longer an issue with Linux" whenever confronted with that fact is full of shit because it still is a dice roll whether or not this specific distro with this specific kernel on this specific machine will work or not. There's always a more lower level, long standing issue with Linux that everyone refuses to pay attention to while constantly glorifying surface level victories like "you can game on Linux". Couldn't care less if the foundation rot is constantly left unchecked. Fix your shit, an OS is meant to be good code first and foremost.

There's a laziness that has set in. I wish it was just indolent distro trannies not wanting to fix something but the attitude has become pervasive. Even if it's not an exact distro issue, acknowledging it makes it one. And these gotchas disapear and runs flawless in stock VMs. Like that's the only standard they work to plus whatever hardware they fetishize personally. If you have a problem then you are not running the *proper* thing which we will not identify publicly until we are outted on a mailing list we can't control.
 

Holy shit this is more ridiculous than I thought it would be.

I guess it's not surprising that Microsoft would do this. 1 that they wouldn't know how to right bash, or they just vibe coded the bash, and 2 that they would allow something that makes them money through their bug (basically some kind of fraud if you ask me), and not fix it immediately.
 
Back
Top Bottom