sparkling arch, sparkling fedora, and diet arch
kogasa
Alternating beans in one grinder willy nilly? Do you have any issues with retention?
Arch teaches you to exercise muscles that would otherwise atrophy. Understanding how your system is put together, how to diagnose and fix problems, how to handle upgrades safely. It becomes just as easy as any other OS and you're better off for it.
It doesn't have any. Fundamental Theorem of Arithmetic applies to integers greater than 1.
Hence why 1 is not considered prime
1, 11, 11*1, etc
Gotta add context for readers.
Of all the numbers to call boring you picked the Grothendieck prime.
2 is unambiguously prime. The best motivation for the definition of primality I know is the fundamental theorem of arithmetic: every integer greater than 1 can be uniquely decomposed into a product of primes. That's what primes are, and the uniqueness constraint is why 1 is not prime.
That doesn't follow. What I think you mean is that by defining the constraints so rigorously, you've basically solved the problem yourself. But that's exactly the point. The LLM isn't the problem solver, it's the execution engine that does the wiring-up and the ticking of boxes. The easy part, arguably, sure. But still considerable effort that can be saved, and that effort may be better spent on the problem-solving + constraint-defining stage.
Mandatory disclaimer that this is not a pro-AI post. I also don't agree that this setup works, anyway. It's a classic Bob Martinism, the idea that writing good enough specifications makes the implementation irrelevant; it's the type of idea that is allergic to reality
pis+rael sent me
Any software born after 2025 should be assumed LLM nonsense until proven otherwise. The days of "there's a working proof of concept so someone must actually have put some thought and effort into it" are gone.
The 3ms figure is nonsense anyway. 2ms of that is just bad scheduling/presentation config that disappeared when using dxvk-low-latency. Use native wayland or Gamescope+WSI and you're within 1ms of X11 generally.
Not CPU limited, actually the opposite. It targets games where the CPU is frequently waiting for the GPU to catch up. It fixes a defect in the AMD pstate driver's active (EPP guided) mode that would cause the CPU to be treated like it's idle if it's often taking short sleeps, even if it's actually quite busy.