this post was submitted on 12 Mar 2026
909 points (98.8% liked)

Programmer Humor

30313 readers
2389 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] kunaltyagi@programming.dev 48 points 13 hours ago (3 children)

The same? Try worse. Most devices have seen input latency going up. Most applications have a higher latency post input as well.

Switching from an old system with old UI to a new system sometimes feels like molasses.

[–] Korhaka@sopuli.xyz 14 points 11 hours ago

I work in support for a SaaS product and every single click on the platform takes a noticeable amount of time. I don't understand why anyone is paying any amount of money for this product. I have the FOSS equivalent of our software in a test VM and its far more responsive.

[–] Buddahriffic@lemmy.world 8 points 11 hours ago (1 children)

Except for KDE. At least compared to cinnamon, I find KDE much more responsive.

AI generated code will make things worse. They are good at providing solutions that generally give the correct output but the code they generate tends to be shit in a final product style.

Though perhaps performance will improve since at least the AI isn't limited by only knowing JavaScript.

[–] boonhet@sopuli.xyz 3 points 10 hours ago (2 children)

I still have no idea what it is, but over time my computer, which has KDE on it, gets super slow and I HAVE to restart. Even if I close all applications it's still slow.

It's one reason I've been considering upgrading from6 cores and 32 GB to 16 and 64.

[–] rumba@lemmy.zip 5 points 9 hours ago (1 children)

Upgrade isn't likely to help. If KDE is struggling on 6@32, you have something going on that 16@64 is only going to make it last twice as long before choking.

wail till it's slow

Check your Ram / CPU in top and the disk in iotop, hammering the disk/CPU (of a bad disk/ssd) can make kde feel slow.

plasmashell --replace # this just dumps plasmashell's widgets/panels

See if you got a lot of ram/CPU back or it's running well, if so if might be a bad widget or panel

if it's still slow,

kwin_x11 --replace

or

kwin_wayland --replace &

This dumps everything and refreshes the graphics driver/compositor/window manager

If that makes it better, you're likely looking at a graphics driver issue

I've seen some stuff where going to sleep and coming out degrades perf

[–] boonhet@sopuli.xyz 1 points 9 hours ago (1 children)

Hmm, I haven't noticed high CPU usage, but usually it only leaves me around 500MB actually free RAM, basically the entire rest of it is either in use or cache (often about 15 gigs for cache). Turning on the 64 gig swapfile usually still leaves me with close to no free RAM.

I'll see if it's slow already when I get home, I restarted yesterday. Then I'll try the tricks you suggested. For all I know maybe it's not even KDE itself.

Root and home are on separate NVMe drives and there's a SATA SSD for misc non-system stuff.

GPU is nvidia 3060ti with latest proprietary drivers.

The PC does not sleep at all.

To be fair I also want to upgrade to speed up Rust compilation when working on side projects and because I often have to store 40-50 gigs in tmpfs and would prefer it to be entirely in RAM so it's faster to both write and read.

[–] rumba@lemmy.zip 3 points 9 hours ago (1 children)

Don't let me stop you from upgrading, that's got loads of upsides. Just suspecting you still have something else to fix before you'll really get to use it :)

It CAN be ok to have very low free ram if it's used up by buffers/cache. (freeable) If Buff/cache gets below about 3GB on most systems, you'll start to struggle.

If you have 16GB, it's running low, and you can't account for it in top, you have something leaking somewhere.

[–] boonhet@sopuli.xyz 2 points 6 hours ago (1 children)

Lol I sorted top by memory usage and realized I'm using 12 gigs on an LLM I was playing around with to get local code completion in my JetBrains IDE. It didn't work all that well anyway and I forgot to disable it.

I did have similar issues before this too, but I imagine blowing 12 gigs on an LLM must've exacerbated things. I'm wondering how long I can go now before I'm starting to run out of memory again. Though I was still sitting at 7 gigs buffer/cache and it hadn't slowed down yet.

[–] rumba@lemmy.zip 0 points 6 hours ago (1 children)

12/16, That'll do it. Hopefully that's all, good luck out there and happy KDE'ing

[–] boonhet@sopuli.xyz 1 points 1 hour ago

Well, 12/32. The rest was being used by Pycharm and Firefox mostly

[–] dr_robotBones@reddthat.com 1 points 7 hours ago (1 children)

Have you gone through settings and disabled unnecessary effects, indexing and such? With default settings it can get quite slow but with some small changes it becomes very snappy.

[–] boonhet@sopuli.xyz 1 points 6 hours ago (1 children)

I have not, but also it's not slow immediately, it takes time under use to get slow. Fresh boot is quite fast. And then once it's slow, even if I close my IDE, browsers and everything, it remains slow, even if CPU usage is really low and there's theoretically plenty of memory that could be freed easily.

[–] silasmariner@programming.dev 1 points 4 hours ago

Have you tried disabling all local Trojans and seeing if that helps?

[–] MashedTech@lemmy.world 2 points 12 hours ago

I want to avoid building react native apps.