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.
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.
Extremely funny. There's a similar situation in math where almost everybody is implicitly using one set of axioms (ZF/ZFC) because they're highly expressive, intuitive, and not known to be inconsistent. There's a hypothetical scenario where somebody discovers a proof that ZF(C) is inconsistent, rendering the vast majority of mathematics "invalid." But nobody is really concerned because on a purely intuitive level, you should be able to transfer the vast majority of mathematics to a different formal basis without issue, since it's all generally done at a different level of abstraction anyway. You'd have to somehow accidentally exploit the inconsistency of ZF(C) to get bit, which is unthinkable. ... Unless you're an LLM, I guess.
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
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.
It would be trivial to add online only drm with a killswitch to physical media. If that's the problem, discs aren't the solution. What we actually need is legal protection for consumers.
Yeah, I'm using them as an example of an underwhelming product that nevertheless has a market at its price, which millions of people regularly purchase knowing how shit it is because the price is tolerable for a guilty pleasure.
Measuring the time in percentages here doesn't make sense. A 1 hour difference on a 3 hour game can easily be chalked up to variance (even the estimate of 3-4 hours has a 1 hour range) but 10 hours off a 30 hour game is enormous. If we also made it $50 instead of $5 and argued for time per dollar as a value metric, sure, those would be equally misleading, but time per dollar is less important as the total cost decreases. Nobody would say a 2 cent movie ticket is half as worthwhile as a 1 cent ticket. They're both approximately as valuable as the experience itself because the cost is negligible.
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.
sparkling arch, sparkling fedora, and diet arch
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
Extremely funny. There's a similar situation in math where almost everybody is implicitly using one set of axioms (ZF/ZFC) because they're highly expressive, intuitive, and not known to be inconsistent. There's a hypothetical scenario where somebody discovers a proof that ZF(C) is inconsistent, rendering the vast majority of mathematics "invalid." But nobody is really concerned because on a purely intuitive level, you should be able to transfer the vast majority of mathematics to a different formal basis without issue, since it's all generally done at a different level of abstraction anyway. You'd have to somehow accidentally exploit the inconsistency of ZF(C) to get bit, which is unthinkable. ... Unless you're an LLM, I guess.
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.
They haven't
It's dithered and possibly smoothed and upscaled, not necessarily AI
It would be trivial to add online only drm with a killswitch to physical media. If that's the problem, discs aren't the solution. What we actually need is legal protection for consumers.
Hop on Arch.
Nothing, bias from the .NET Framework days probably
Yeah, I'm using them as an example of an underwhelming product that nevertheless has a market at its price, which millions of people regularly purchase knowing how shit it is because the price is tolerable for a guilty pleasure.
Measuring the time in percentages here doesn't make sense. A 1 hour difference on a 3 hour game can easily be chalked up to variance (even the estimate of 3-4 hours has a 1 hour range) but 10 hours off a 30 hour game is enormous. If we also made it $50 instead of $5 and argued for time per dollar as a value metric, sure, those would be equally misleading, but time per dollar is less important as the total cost decreases. Nobody would say a 2 cent movie ticket is half as worthwhile as a 1 cent ticket. They're both approximately as valuable as the experience itself because the cost is negligible.
It's $5 full price and advertised as typically 3-4 hours long. A big mac is over $6.