schizo
I assume the KDE implementation resizes to default when you stop shaking it.
I could totally see someone coding a function that increases the mouse pointer by x% every y mouse shakes, and then neglecting to put in a size cap.
This is kinda old information, but my understanding was that there were 3 issues with dasiy-chained UPSes.
The first is that you're potentially going to cause a ground loop, which is not healthy for the life of anything plugged into those UPSes.
The second is that there's a potential for a voltage droop going through from the first to second UPS, which means the UPSes will flap constantly and screw their batteries up, though I'd be shocked if that was necessarily still true for modern high-quality units.
And of course, the UPS itself won't be outputting a proper sinewave when it's on battery, which means your 2nd UPS in the chain will freak out (though again, maybe modern ones don't have that limitation).
Yeah, and Windows and OS X both do it as well.
Though there being no upper limit to the size is amusing.
I gather that's a meme that's older than you are?
By linux ISOs I meant any content you're torrenting: movies, software, audio, my little pony porn, whatever.
Frankly, it probably means absolutely nothing.
Even when captain coffee cup was the FCC chairman, did you lose the ability to torrent linux isos? Did usenet stop working?
I wouldn't expect anything different this time, either.
Yeah, it doesn't appear that PSSR (which I cannot help but pronounce with an added i) is the highest quality upscaling out there, combined with console gamers not having experienced FSR/FSR2/FSR3's uh, specialness is leading to people being confused why their faster console looks worse.
Hopefully Sony does something about the less than stellar quality in a PSSR2 or something relatively quickly, or they're going to burn a lot of goodwill around the whole concept, much like how FSR is pretty much considered pretty trash by PC gamers.
really effects performance that much
Depending on the exact flags, some workloads will be faster, some will be identical, and some will be slower. Compilier optimization is some dark magic that relies on a ton of factors, but you can't just assume that going from like -O2 to -O3 will provide better performance, since the optimizations also rely on the underlying code as to what they'll actually make happen... and is why, for the most part, everyone suggests you stop at -O2 since you can start getting unexpected behavior the further up the curve you go.
And we're talking low single digit performance improvements at best, not anything that anyone who is doing anything that's not running benchmarks 24/7 would ever even notice in real world performance.
Disclaimer: there are workloads that are going to show different performance uplifts, but we're talking Firefox and KDE and games here, per the OP's comments.
Also they do default to a different scheduler, which is almost certainly why anyone using it will notice it feels "faster", but it's mainlined in the kernel so it's not like you can't use that anywhere else.
AI slop? On my website full of mostly garbage articles? Well I never.
A barrel of laughs if you bring your own barrel, anyway.
Does !12345:p do what you want?
Edit: that also makes hitting the up arrow result in whatever command that was, so if you wanted to edit the line or whatever, you could !12345:p, up, then edit and execute.
Honestly, I would have assumed 1080p was an acceptable default assumption.
Is this just a case of older hardware, or are there still laptops that don't have 1080p panels at this point?
A quick review of stuff on BestBuy indicates that $150 laptops have 1080p displays now, and anything more than that does as well, so uh, what devices are still using these?