

./clears_throat.sh
I can neither confirm, nor deny that I am in fact D̵̡̮̻̗̖̮͔̜͈̙͖͙͍̺̀̒̍̌̑͐̓͡å̴̲͍̋̉́̀̑͊̎̐̊͡l̴̟̭̳̄̅̕͝͠͝ȩ̸͚̼̘̫̺̻̬̻̮͖̣̬̖̠̗̎̌ ̵̯͕͛́͋͌̀͝͠ͅͅG̷̛͈̩̟̟̠͓̗̘͓͍̽̒̌̔̓̈͗̐̈̿͠͠r̷̘̞̹͂̀̑̋̀͌̍͗̆͝͠͝ͅi̶̡͔͖͍̟̲̮͑̎͌̀̎b̵̡̢̹̗͔̗͍̘̣͊͊̑͒̍̑͌̽͋͌̔͝͝b̷̭̩̩̣͙̺͎̱̗͙͚̩̈́l̸̛͎̼̟̋͆͆͗̓̓̓͘͟ĺ̶̼͇͎̫̮͎̣̳͉̯̊̆̂̓̄̍̃̚e̶̢̡̛̫̣͈̺̾̅͐̾̓͒̚ͅ.̴̫̞̥̒̈̇̓́̾͗̒́̉̔͑
./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 |
+-----------------------------------------+------------------------+----------------------+
Is Yiddish basically Hebrew + Street/Slang German? I guess I could look it up, but I thought I’d just ask.
Making fun of people has more “stank” in English (not a hard fact, just my opinion).
Zed and Helix for the GNU/Linux side, and VSCodium for the Windows side.
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 😅…
x11vnc
, when I finally come back to it after trying damn near every remote desktop application on the market: