181–190 of 328 posts
Earlier quoted context omitted.
The best thing about Win10 reaching EOL is not being at the mercy of Windows Update any more. It was by far the biggest risk to having a functioning system.
Running an unsupported OS is even more risky, especially with the excessive number of security updates needed while AI finds RCE after RCE.
Earlier quoted context omitted.
What's your setup like? I'm on AMD+Wayland+KDE, no complaints with fractional scaling on my ASUS ProArt PX13 (255 PPI screen).
In my laptop 200% fractional scaling of the built-in QHD+ OLED display on KDE Plasma is great, but when I connect my portable 1080p displays or e-paper monitor (UXGA) the fractional scaling of it is not as good as when compared to when the same monitors are used with macOS (M4) in HiDPI mode under lower resolutions. As the other comment says, I suspect it to do with GPU as the built-in displays are usually driven by…
Gosh, 7.2 literally just dropped with a bunch of awesome of performance/gaming related improvements (large folios, cache-aware scheduling, improved MGLRU reclaiming, Fair GPU Scheduler etc)... and I already can't wait for 7.3 to come out. Meanwhile in the Windows world, users hate updates... Like I genuinely can't think of a single instance that made users exclaim, "oh boy I just can't wait for the next Patch Tuesday…
The best thing about Win10 reaching EOL is not being at the mercy of Windows Update any more. It was by far the biggest risk to having a functioning system.
Great article! I share the same hunch as the author does; when allocating memory ultimately the application itself is in the best position to inform the kernel about the desired stickiness to VRAM. The best a kernel can do is guessing . As a side note, it strikes me how much we owe to young trans people for low level performance engineering.
They'll get old soon enough.
Earlier quoted context omitted.
From my experience, Windows does freeze and become completely unusable too, just not usually from RAM usage hitting 100%. I don't use Windows much, nor do I care much about that environment, but from what I've seen it seems to keep RAM usage below 100% most of the time. What I do see pretty often is the drive getting stuck at 100% usage instead, which makes the whole system ridiculously unusable anyway.
Windows uses eager memory allocation, and applications will die when they allocate (and think image editor loads a beefy image) or fail to start when it runs out of memory. Linux uses lazy allocation and overcommits, so what dies isn’t necessarily what you would expect thanks to the OOM killer. With a fixed swap size windows doesn’t necessarily slow down as it runs out of memory. YMMV if you don’t have 64 gigs of RAM…
It's VRAM, not vRAM.
Earlier quoted context omitted.
I imagine "we" "owe" a lot more to young men or just men in general for the same, but I guess there's no virtue signaling points to be harvested from making that observation.
It seems my praise was hurting you. Let me praise some people from an unrelated project: we owe a lot to the greybeards keeping Scribus alive. And you are right, we owe a lot to all kinds of people. To quote myself from another comment: «I am inclined to rather point out remarkable things than unremarkable things. There seems to be relatively many trans people in this niche.» That's all. I didn't know this required a…
Earlier quoted context omitted.
macOS too sadly. by the time you realise there's a problem the machine is already comatose and unresponsive all these electron apps and invisible virtual machines (looking at you Claude) really don't help.
One of the biggest reason I migrated to Codex. I'd like to see each agentic CLI process as a simple building block, and having 100 claude session means I sometimes run out of memory (and I have 256GB of them). Codex never have this problem. The communication is more direct too with GPT5.6 family of LLM. No more belt and suspenders.
I hope there will be an update where when my RAM gets full my PC doesn't freeze and becomes unusable... I remember that Linux and Windows do this in different ways and Windows doesn't have the problem.
I now have btop permanently running in a Terminal and I habitually Alt-Tab to it to watch my swap. As soon as my free memory gets less than 1 Gb I kill any Firefox tabs (the memory black hole).
I know this won't be popular, but Linux people have some kind of Stockholm Syndrome on this. They tell you all of the obscure configuration files you have to edit, the additional programs you install. They insist that just having the OS kill a random program to save the DE is a good plan. It's the typical "your holding it wrong" mantra.
I run both Windows and MacOS and have done so for decades. I cannot remember the last time I had a hard freeze like I get on Fedora. On the exact same box running Windows I was able to have VS Code, Chrome with 15+ tabs, terminals, docker, etc. all running with zero issues. On Fedora I have a handful of Terminals and Firefox with less than ten tabs and nothing else running and I have to watch btop like a hawk.
The excuses people make are mind bending, and the shifting of blame from the system onto the user is shameful.