

Fuck that.
Too many people with brittle spirits performatively clutch their pearls to the point of banality when they’re called out on it.
I can neither confirm, nor deny that I am in fact D̵̡̮̻̗̖̮͔̜͈̙͖͙͍̺̀̒̍̌̑͐̓͡å̴̲͍̋̉́̀̑͊̎̐̊͡l̴̟̭̳̄̅̕͝͠͝ȩ̸͚̼̘̫̺̻̬̻̮͖̣̬̖̠̗̎̌ ̵̯͕͛́͋͌̀͝͠ͅͅG̷̛͈̩̟̟̠͓̗̘͓͍̽̒̌̔̓̈͗̐̈̿͠͠r̷̘̞̹͂̀̑̋̀͌̍͗̆͝͠͝ͅi̶̡͔͖͍̟̲̮͑̎͌̀̎b̵̡̢̹̗͔̗͍̘̣͊͊̑͒̍̑͌̽͋͌̔͝͝b̷̭̩̩̣͙̺͎̱̗͙͚̩̈́l̸̛͎̼̟̋͆͆͗̓̓̓͘͟ĺ̶̼͇͎̫̮͎̣̳͉̯̊̆̂̓̄̍̃̚e̶̢̡̛̫̣͈̺̾̅͐̾̓͒̚ͅ.̴̫̞̥̒̈̇̓́̾͗̒́̉̔͑
Fuck that.
Too many people with brittle spirits performatively clutch their pearls to the point of banality when they’re called out on it.
Operational security requires robust peer review of codebases and their potential vulnerabilities. Small distributions haven’t had the scale of scrutiny required to entrust them with incoming, outgoing, and stored private information.
Linus doesn’t have to be a dick all the time. However, as I get older, I begin to understand the wisdom behind a monologue in Team America: World Police more and more:
We’re dicks! We’re reckless, arrogant, stupid dicks. And the Film Actors Guild are pussies. And Kim Jong Il is an asshole. Pussies don’t like dicks, because pussies get fucked by dicks. But dicks also fuck assholes: assholes that just want to shit on everything. Pussies may think they can deal with assholes their way. But the only thing that can fuck an asshole is a dick, with some balls. The problem with dicks is: they fuck too much or fuck when it isn’t appropriate - and it takes a pussy to show them that. But sometimes, pussies can be so full of shit that they become assholes themselves… because pussies are an inch and half away from assholes. I don’t know much about this crazy crazy world, but I do know this: if you don’t let us fuck this asshole, we’re going to have our dicks and pussies all covered in shit!
In this case, Linus is a dick who fucks when it’s not appropriate a lot (i.e., is harsh in his critique about bad code in pull requests). Assholes push bad code, and sometimes it’s so bad that it’ll fuck up the whole kernel. Pussies in tech magazines criticize his style of critique. Other pussies get “butt-hurt” because they code like shit too and they can’t or won’t admit it, and they’re so full of shit, they’re pussies who’ve become assholes themselves.
The code in question is, in fact, garbage.
x11vnc
, when I finally come back to it after trying damn near every remote desktop application on the market:
./clears_throat.sh
I use X11 over Wayland on KDE Neon for RustDesk compatibility. The Wayland support for that application is still in Beta from what I understand.
Are there other reasons why I should keep X11? I am on AMD Ryzen 9 5950X paired with a RTX 3090 FE on 570-open
drivers, for reference.
Oh, here comes the genius motherfucker with the big-brain counterargument: “Well, if HTML’s so great, why not just write everything in Assembly, huh?”. Wow, look at you, you clever little prick. Did you come up with that all by yourself? Writing web pages in Assembly is like using a fucking scalpel to slice your overcooked steak: sure, it’ll get the job done, but you’re gonna look like a complete asshole while you’re at it. HTML just works, you absolute tool. It’s been the backbone of the web since Al Gore flipped the switch, and it’ll still be here long after your trendy framework is rotting in a GitHub graveyard. So take your smartass logic and shove it. HTML’s king, and you’re just a peasant with a keyboard.
🤣
I assume I’m safe as a Kubuntu enjoyer?
After strolling through blogs and forums, I still can’t tell what I’m missing by sticking with SDDM+X11 versus SDDM+Wayland on Kubuntu 24.04 LTS (--minimal-install
, so no snap
for me).
These are my specs:
-----------------
OS: Kubuntu trixie/sid (noble) x86_64
Kernel: 6.8.0-58-generic
Uptime: 1 hour, 12 mins
Packages: 2 (npm), 2550 (dpkg), 28 (flatpak-system)
Shell: bash 5.2.21
Resolution: 1920x1080 @ 164.92Hz
DE: Plasma 5.27.12 [KF5 5.115.0] [Qt 5.15.13] (x11)
WM: KWin
Theme: klassy [KDE/Qt], Breeze [GTK2/3]
Icons: BeautySolar [KDE/Qt/GTK2/3]
Cursor: breeze_cursors [GTK2/3]
Terminal: konsole
Terminal Font: Noto Mono 12
CPU: AMD Ryzen 9 5950X (32) @ 3.4GHz
GPU: NVIDIA GeForce RTX 3090
Memory: 4.15 GiB / 31.24 GiB (13%)
Network: Wifi
Bluetooth: Intel Corp. AX200
BIOS: American Megatrends Inc. 5.17 (03/18/2024)
Sun Apr 27 13:03:03 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.133.07 Driver Version: 570.133.07 CUDA Version: 12.8 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 3090 Off | 00000000:0A:00.0 On | N/A |
| 0% 47C P0 43W / 350W | 714MiB / 24576MiB | 2% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
Making fun of people has more “stank” in English (not a hard fact, just my opinion).
Ah okay, specific for Gentoo, I see. Thus, since I’m in *buntu land (--minimal-install
, so no snap
fuckery), it’s better to just set up an apt
repo and use my build containers to push to that.
I personally love Rust, but since I’m already familiar with C/CMake, I just don’t think I need to “re-invent the wheel”. In this case, using the Rust wrapper option is more like “trying to put a winter tire around an all-weather tire”.
Any similar system for Kubuntu 24.04 LTS noobs/normies like me? I don’t know what “ebuild” is, but it sounds cool (of course, I could look it up, but I thought I’d just ask).
I’m not a dev-ops dude, but for work, I develop parametric CAD solutions and generative DNNs for CAD. Lots of linear algebra and Pytorch on the GNU-Linux side; lots of Grasshopper for Rhino8 on the Win11 side. Hence, I use Docker to separate my experimental build environments from my production ones.
I’ve been kinda maintaining my shit “by hand”, so to speak, for years now, and I think I’m ready for some automation in that regard.
- libsnorble-2-dev, a C library that the author only distributes as source code and therefore must be compiled from source using CMake
Of the available options, this is easily the best since I can use my own compilation flags to tune the library for my specific target architecture/CPU which can possibly change as the deployment profile for the business case evolves. Assuming it’s OSS, I can also fork and adjust the library itself for said “mission-critical” use case.
Also, the Google product being deprecated since '17 is too real 😅…
I think a lot of the plugin tooling for Unreal promotes bad practices with asset management, GPU optimization, and memory management. I’m trying to say that it allows shitty/lazy developers and asset designers to rely on over-expensive hardware to lift their unoptimized dogshit code, blueprints, models, and textures to acceptable modern fps/playability standards. This has been prevalent for a few years but it’s especially egregious now. Young designers with polygon and vertex counts that are out of control. Extraneous surfaces and naked edges. Uncompressed audio. Unbaked lighting systems. Memory leaks.
I’ve found that in my personal experience in experimenting with Unreal, the priority matches developing DNNs and parametric CAD modelling applications for my day job: effective resource, memory, and parallelism management from the outset of a project is (or should be) axiomatic. I think Unreal 5 runs exceptionally well when that’s the case. A lot of the time, one can turn off all of the extra hardware acceleration and frame generation AI crap if your logic systems and assets are designed well.
I know this is a bit of an “old man yells at cloud” rant, but if one codes and makes models like ass, of course their game is gonna turn out like ass. And then they turn around and say “tHe EnGiNe SuCkS”.
No. Fuck you. You suck.
“SyStEmD iS bLoAt…”
I think “coasting” is a bit too strong.
Furthermore, to clarify, I think people should be allowed to be dicks (verbally). I also think they should face the consequences of being a dick.
Nerfing “toxic” language with the weight of law is too much, but public shunning and/or an employer’s ire are absolutely consequences that people should face with the same stoic fearlessness that they purport to have when they’re being dicks to other people. In this case, (I think) he is the owner of the kernel repository. His word is in fact law when it comes to pull requests. He can be a dick if he wants to, so long as it complies with Finnish law on slander, libel, inciting violence, etc. And, of course, we, the public, are free to judge him on it.
I read what he said. I also read the pull request in the code that he was talking about. I also noted how late the pull request was submitted. He’s harsh but also absolutely right, in this case.
What I can’t stand is the performative pearl clutching and virtue signaling that people love to masturbate to.
It’s a simple premise. As said in the gif I posted, “He’s outta line, but he’s right.”