It's not 2000 Vs 2048. It's 1,862 Vs 2048
The GB get smaller too.
wewbull
joined 1 year ago
Which nobody uses in the industry because we all know that storage uses base2 prefixes.
Kilo meaning 1,000 inside computer science is the retcon.
Tell me, how much RAM do you have in your PC. 16 gig? 32 gig?
Surely you mean 17.18 gig? 34.36 gig?
They were consistent until around 2005 (it's an estimate) when drives got large enough where the absolute difference between the two forms became significant. Before that everyone is computing used base 2 prefixes.
I bet OP does too when talking about RAM.
there is nothing intrinsically base 2 about hard drives
Yes there is. The addressing protocol. Sectors are 512 (2⁹) bytes, and there's an integer number of them on a drive.
Errrm, could they please leave some memory to other processes? KDE already takes about 1.5GB of VRAM on my RX7600 8GB just running a desktop (dual head 4k + 1440p displays). Yes, things can get swapped out to main memory, but that becomes choppy. I'd rather run single buffered, get the odd screen tear, and have the VRAM back for real work.
What the hell are you prompting to get something like that? I'm guessing "parliament of owls" is in there somewhere.
I think this one needs a detailing pass.
I'm pretty sure this has been a real thing in some Muppet movie or other.
The problem here is that you have the token "eyes" with very heavy weighting, and it's showing you eyes. Another way of thinking about it is...
What do you see when somebody closes their eyes? Eyelids
Also, finding an exploit means the system will get stronger very shortly.
So design one that's easily cleaned. E.g. you throw it in a bucket of chemical X for 15 minutes. Battle field hospitals would rather have 50 cleanable items than 5,000 disposable ones. Far easier to transport.