The Linux Thread - The Autist's OS of Choice

  • 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'm inclined to agree, to an extent. I think it was purposefully done to incite groups like the Artix Linux people into taking his side, which to his credit, definitely worked. It's a double edged sword. On one hand it gives him a ' he can get active, dedicated support, while on the other it might alienate people who would otherwise be supportive if not for his whole anti-DEI spiel. I certainly support it. Fuck Red Hat and fuck IBM, compromise is the first nail in the coffin, so the more unabashed and loud people are against them, the better. Plus, I think the project will see slow burn support from even people like Devuan, FreeBSD and Antix (once they get properly buck broken) since X11 is effectively dead in the water.
My criticism of it. Is they could have done that. Without explicitly stating it. And having artix on their side is good. But if they didn't add that extra bit of a reason to have other projects shun them. They could have potentially had a lot more support from the start. Artix overall isn't huge project. I think just having the anti-redhat stuff would have been enough to give people a general idea of where the project stands. While not being as bad if an optics move.

I was saying a few posts up. It's not just people that have a problem with the no dei thing that will be pushed away. It's people that are worried about the optics of helping a project that makes that something they care about enough to put in their readme.

As if they don't ostracize and alienate people with their "Code of Conducts". Ironically, that anti-DEI thing in the README is sort of a Code of Conduct itself, though clearly different in nature compared to the tranny-written """Contributor Covenant""" which serves only to purge whoever they see as "Nazis" and "facists".


Personally I'm alienated by projects which adopt Code of Conducts like the """Contributor Covenant""" but that might just be me.
I don't care about people feeling alienated. Or peoples feelings in general in this situation. It's about the way that will be weaponized to hurt the projects chances of being adopted.

And I absolutely do expect it. I've seen these people come out of nowhere with shit to try and kill projects the deem against their ideals.

Just because I like that a project says no retarded politics, or dei shit. Doesn't mean it's a good move, and in general it's a really dumb thing to do. If you just want a project to succeed on its merits. Because ironically it immediately brings politics into it.
 
It's so weird seeing people have issues with Nvida while I'm here just fine, not experiencing anything wrong.

My first experience with Wayland was accidently using it on a new KDE Plasma installation. Before, I would use Xorg only, not because of philosophical reasons, but because I thought Wayland was some esoteric technology that required specific knowledge about Linux or whatever (I was/still am a Linux noob. No bully, plz).

Wayland actually solved a lot stuttering I was experiencing with Linux, which was a big issue for me on Linux. Everything felt so smooth and responsive compared to Xorg.

I tried Xorg on Plasma again to see if the stuttering/responsiveness issues I was experiencing was just me making shit up, but it wasn't. It was all still there, just like how I remembered it. I don't know if issues on Xorg that get fixed with Wayland is an Nvida exclusive but, even if it is, I'm still gonna use it because it's the best for me and I don't care about philosphical reasons.
That's fair. But Nvidia optimus is notoriously incompatible with Wayland. Nvidia-Prime, the official recommended solution, has issues on wayland and not x11.

People hate Wayland because of the smug and condescending freedesktop\RedHat\Gnome politburo that forces security over freedom of choice. Also it promotes fragmentation. If someone wants to create a new DE, they need to implement all these shitty Wayland protocols by themselves. I know there exists wlroots, but thats a piece of shit.
 
Last edited:
That's fair. But Nvidia optimus is notoriously incompatible with Wayland. Nvidia-Prime, the official recommended solution, has issues on wayland and not x11.
Is that for laptops? I've never owned a laptop (Well, only a shit, extremely underpowered one) so I don't have any knowledge or experience with it.
 
ROCm will be viable on the same day Wayland becomes viable. :smug:
Rocm is in the same position amds... everything is. I've used it for just about everything you use Cuda for, at least for normal users without specialized software. (Blender mostly nowadays, but I did test out AI image and text.)

It's like everything AMD makes, good enough to use, slower than Nvidia. Hopefully it gets better in the future. HipRT finally almost made my gpu usable for complex blender renders, but it has its bugs sometimes.
 
And I absolutely do expect it. I've seen these people come out of nowhere with shit to try and kill projects the deem against their ideals.
That's why telling them to piss off on day one is a good idea. We both know that, if a project doesn't die in the first month, these fuckers will pop up like like mushrooms to try and subvert it. This way people can tap the "no DEI" sign and get back to work.
 
That's why telling them to piss off on day one is a good idea. We both know that, if a project doesn't die in the first month, these fuckers will pop up like like mushrooms to try and subvert it. This way people can tap the "no DEI" sign and get back to work.
Let's say he didn't. Trannies and progressives contribute. And the do try that. Why wouldn't he just be able to cut it off then? Kick contributors that insist on bringing politics to the project.

I probably need to look into the gnu stuff again. But from what I recall they did try to subvert gnu. Gnu only cares about free software not about retarded gay nigga politics. So they ended up turning on gnu down the line. But gnu still isn't know explicitly as non-dei. (This is just from memory, and there is a lot more to it. But that's basically what I remember the being the gist of it)
 
More and more projects against the wokeshit CoC(k) are going to advertise their own resistance just because it's gotten so bad and isn't getting any better. I wouldn't be surprised if more Linux distributions that openly resist a Cock of Conduct and other DEI-ism crop up here and there.
 
Let's say he didn't. Trannies and progressives contribute. And the do try that. Why wouldn't he just be able to cut it off then? Kick contributors that insist on bringing politics to the project.
Didn't work out well for the PolyMC guy:
PolyMC & Forks
For some time, PolyMC was the most popular minecraft launcher that's basically a modified version of MultiMC. This was until October 2022, when several developers were purged from the PolyMC team for promoting as the main contributor describes "radicalist leftist queer ideology". This purge of the contributors led to the tranny developers on the team to maliciously lie and claim that PolyMC had malware on it. This lie even being parroted by minecraft developer Kingbdogs. The only ones to call them out on their bullshit were anons on /g/. Of course, in the minecraft sphere they actually got away with it because most of these spergs technologically illiterate and nobody there actually audited the GitHub repository.
1710277396311.png
1710277555788.png

This led the same troons who were kicked off the PolyMC team to create a fork known as Prism. Which despite being a PolyMC fork became plagued with issues such as memory leaks and zip file path traversing issues [A] with a 7.8 severity rating that's still unresolved after a full year of it being detected. Meanwhile when people try to give them actual good code, they completely disregard good code because the guy who made it is a big ol' stinky meanie head™. I don't know about you guys, but I'll take a single Terry A. Davis over ten soy devs personally speaking. This isn't even mentioning how a few people in the Prism discord attempted to hijack the /mmcg/ thread on /vg/ on an occasion and fail miserably.
1710819970718.png

Because of this reputational damage that Prism did to PolyMC, their CurseForge token was revoked, their donation page was suspended, and their reputation was turned into a pile of smoldering ashes. All of this was because the Main Developer did not want a code of conduct for what is supposed to be a FOSS Project.
 
More and more projects against the wokeshit CoC(k) are going to advertise their own resistance just because it's gotten so bad and isn't getting any better. I wouldn't be surprised if more Linux distributions that openly resist a Cock of Conduct and other DEI-ism crop up here and there.
I wonder if that will lead to a schism in the community that literally ends up with incompatible codebases.

What's the best distros that don't have systemd?
 
I wonder if that will lead to a schism in the community that literally ends up with incompatible codebases.

What's the best distros that don't have systemd?

"Best" is a bit of a muddy basis to work with.

Alpine Linux (non-GNU) doesn't enforce any hugely opinionated defaults from what I've seen, and you can use a simple script to bypass session bus errors when not using elogind, or use seatd instead and go from there. Antix (GNU) is the lighter half of MX Linux and you use window managers instead of full desktop environments, and it doesn't rely on elogind whatsoever.
 
Let's say he didn't. Trannies and progressives contribute. And the do try that. Why wouldn't he just be able to cut it off then? Kick contributors that insist on bringing politics to the project.

Isn't that more or less what's happening? This isn't an attempt to re-write X11 from scratch, just to get some changes in. That this goes against "the agenda" is why it was necessary to fork it. Unless I've missed it, there no requirement to actually be anti-troon.

I probably need to look into the gnu stuff again. But from what I recall they did try to subvert gnu. Gnu only cares about free software not about retarded gay nigga politics. So they ended up turning on gnu down the line. But gnu still isn't know explicitly as non-dei.
Gnu is probably a fringe case, because it has its own purity death spiral over (for lack of a better word) "freeness".
 
I've been giving i3 a try, (I just have it as an option, I'm mainly using KDE plasma), but I've been noticing that I find it awkward to use outside of certain workflows. Namely, I find it the most ergonomic when I'm doing development stuff, but with something like a file or web browser open, I find it a lot less comfortable to use, and the clashing of styles between different programs is a lot more noticeable.
Am I getting filtered or is there something I could do about this? I do genuinely like it when I have just a bunch of terminals and an editor open.
 
Personally I'm alienated by projects which adopt Code of Conducts like the """Contributor Covenant""" but that might just be me.
Oh no, I'm 100% with you there. Hence my love for OpenBSD and Obarun, both of which have essentially zero CoCs.

I wonder if that will lead to a schism in the community that literally ends up with incompatible codebases.

What's the best distros that don't have systemd?
I was schizoposting about this like ~5 pages ago. Lemme give you a TLDR:
- OpenBSD/FreeBSD have 0 systemd creep so are great by default
- Obarun Linux is a smaller arch-based distro run by an extreme anti-systemd schizo, def my #1 OS of choice, currently tidying up before I swap my main machine over to it
- Antix Linux also has 0 systemd components but is run by actual Antifa people; if you can look past that it is an excellent debian based, minimalist distro
- Gentoo if you are willing to use heavily restrictive USE flags to disable all sysd components
- Same with Artix, you can achieve this with out too much difficulty by using the s6 version and cutting out elogind and dbus, but if you are already that motivated, you might as well just use Obarun

That's my shake on it. Just keep in mind that if you truly purge ALL sysd components you'll be relegated to using window managers like i3 or DWM because pretty much all DEs require some systemd elements. This blog here has other excellent choices if you want to peruse: https://sysdfree.wordpress.com/2025/06/09/363/

I've been giving i3 a try, (I just have it as an option, I'm mainly using KDE plasma), but I've been noticing that I find it awkward to use outside of certain workflows. Namely, I find it the most ergonomic when I'm doing development stuff, but with something like a file or web browser open, I find it a lot less comfortable to use, and the clashing of styles between different programs is a lot more noticeable.
Am I getting filtered or is there something I could do about this? I do genuinely like it when I have just a bunch of terminals and an editor open.
One word: keybinds. While I run DWM instead of i3, you can rig a keybind to swap you to a new workspace and drag or open your browser in there, if that's what you meant. For a more rice-friendly browser, may I suggest Qutebrowser? Very clean, very light, and very fun to use if you know your vim. Probably the most riceable browser you can find right now tbh, definitely far and away better than chromium/firefox.
 
One word: keybinds.
Honestly the keybinds aren't a huge issue, I've been using tilix and emacs for years, so splitting isn't crazy for me. Biggest learning curve on that front is the different 'flow' for choosing vertical / horizontal splitting.
On emacs, you do `C-x [2/3]` for vertical and horizontal splits respectively, while i3 has the weird passive toggle with `M-[v/h]` followed by opening something. It's just a bit easy for me to space on that.
 
Call me late, retarded, etc, but nobody who:

1. Can actually write good code
2. Knows the merits of X11 and Wayland, and the bad parts of both
3. Has actually interacted with the X codebase and has written apps and windowing abstractions for X

actually wants to maintain xserver or any X11 tool. Even today, xwayland is the worst part of Wayland to develop because X11 sucks from a technical perspective. It's old, and doesn't make sense anymore as we run everything on the same machine, shared terminals are a thing of the past.

Ask yourself why we still have 1 xserver implementation (after what, 30+ years of it being dominant?), and how Wayland has a plethora of different and compliant implementations[1] and why even the technically-able non-woke compositor developers are developing for Wayland.

Defending bad tech just because it's not woke just makes "not woke" look stupid. Nobody takes Lunduke seriously, and I personally don't either because of this.

XLibre is mostly a meme & is even less secure than X11, the developers aren't competent. If you want a "chud" and anti-DEI windowing system, you can just use Hyprland.

[1]: wlroots (debatable quality), Hyprland's own thing, Smithay. And these are only the Wayland compositor-related libraries/compositors themsevles, Wayland RPC has a lot more implementations because it is a very simple and efficient event-based protocol - even Chromium uses it for communication between tabs and the browser (if I remember correctly. may not be chromium, but you can use it like that).

PS: Fuck GNOME and Freedesktop for impeding the progress of Wayland, their security theater and unwillingness to stabilize Wayland protocols. They are the #1 reason progress is slow.
 
Last edited:
nobody who:

1. Can actually write good code
2. Knows the merits of X11 and Wayland, and the bad parts of both
3. Has actually interacted with the X codebase and has written apps and windowing abstractions for X

actually wants to maintain xserver or any X11 tool.
Take a look who "develops" Xorg. Oh wait, its the Wayland guys!
There cannot possibly be a conflict of interest there!
Ask yourself why we still have 1 xserver implementation (after what, 30+ years of it being dominant?), and how Wayland has a plethora of different and compliant implementations
The plethora of different Wayland implementations is not a good thing, and I'm tired of pretending it is.
Try taking a screenshot in Wayland. In KDE, only Spectacle works. In Gnome, only gnome-screenshot works. If you don't like it, tough shit!
Other programs like grim/slurp you may want to try only work on wlroots.

Having millions of implementations wouldn't be a deal breaker if basic things like screenshots and keyboard input were part of base Wayland (like how everything basic is in X), but these have been rejected time and time again because it would make Wayland "too similar to X".
Funnily enough if everyone standardised on a single Wayland implementation way back then, X would probably be long in the grave by now. But that's not happening.
Every time a Wayland shill says X is dead, X lives for another day.
 
Back
Top Bottom