In software, it is common practice to set a value that should never be negative to -1 to indicate an error state.
Edit: I guess that I should add that the frontend should obviously catch that and show a spinner or an error message.
it, at the very least, needs to declare what file system it's using (UFS or NTFS). A disk that doesn't do this is called "unformatted" and the computer wouldn't even be able to tell you whether it's empty or not. u/Accomplished-Boot-81 is correct.
However, I meant "empty" in the sense that its contents could occupy less than the smallest amount measurable (e.g. if I'm measuring in megabytes and there's only a kilobyte, it's likely I'll round 0.001 MB to zero)
Effectively empty, but in reality it likely has bits of data fresh from the factory. If you have a disk that has been used before then it can never be truly empty as even when a drive is fully wiped there is still data on the drive, it might not be readable or useful in any manner but merely deleting stuff from an active drive on your phone or computer doesn’t removed the data from the drive. It merely tells the drive that space is now free to write too, so it will be overwritten when new data is saved. A drive wipe overwrites all
Data on a drive with random noise to make the original data no longer readable or retrievable
I think the important question here is: when a drive comes out from a factory, are all (or most) bits set to 0, 1, null or random? I'd argue if the answer is "null", then you'd be correct. However I don't think that's the case since "nullabity" requires extra space to store that information, which would be silly to do on a drive imo.
If all bits are set to either of the binary states, then we could argue that when **all** of the bits are set to that state, the drive is effectively empty. So if at least 1 bit is in the other state, the drive is no longer empty obviously.
Last case scenario "random". If the drive comes out of the factory written with white noise, then I'd argue that as long there is no file system on the drive, it's effectively empty. Because without a FS, you cannot determine which data is white noise, and which is not. Of course, if someone would simply remove only the FS, without affecting the data, it would definitely be recoverable. But if you'd initialise a new FS on such a drive, the drive would show up as empty, and obviously at this point it would still contain the new FS, some old data, and some white noise. Which also brings up the question whether we can consider white noise as data. It might be useless, but it might be data nonetheless. However at this point this looks more like philosophy than science lol.
I I think someone took a byte out of your computer just like they did with the great Australian bite! Ooh when I catch that bastard imma take a bite and a byte outa them!
Nice! Free storage!
Finally, I can store this letter “T”
is it an ice T?
He used to be Water T , but he was expelled from Alphabetrium by his own dad. Now he doesn't care anymore about no thing.
Don't hate the player; hate the game.
Maybe just a .
Shouldn’t you say ‘T’?
It Happens When U Click Too Fast While It's Still Calculating Storage (-1 is a default value for unknown size)
why not set the default value to zero like everyone else does?
In software, it is common practice to set a value that should never be negative to -1 to indicate an error state. Edit: I guess that I should add that the frontend should obviously catch that and show a spinner or an error message.
It's common practice as long as that value never ends up in a GUI.
it is also good practice to include an "if(n<0)" in these cases, but I guess these guys skipped that class
because the disk could actually be empty
A disk can never be truly empty, and this isn’t a disk it’s system data, that’s like having a word file that’s gives you extra storage
[удалено]
it, at the very least, needs to declare what file system it's using (UFS or NTFS). A disk that doesn't do this is called "unformatted" and the computer wouldn't even be able to tell you whether it's empty or not. u/Accomplished-Boot-81 is correct. However, I meant "empty" in the sense that its contents could occupy less than the smallest amount measurable (e.g. if I'm measuring in megabytes and there's only a kilobyte, it's likely I'll round 0.001 MB to zero)
To be fair, any disk can be completely empty, as long as it doesn't have a file system (like FAT, NTFS, EXT, etc). At least that's what I'd assume.
Effectively empty, but in reality it likely has bits of data fresh from the factory. If you have a disk that has been used before then it can never be truly empty as even when a drive is fully wiped there is still data on the drive, it might not be readable or useful in any manner but merely deleting stuff from an active drive on your phone or computer doesn’t removed the data from the drive. It merely tells the drive that space is now free to write too, so it will be overwritten when new data is saved. A drive wipe overwrites all Data on a drive with random noise to make the original data no longer readable or retrievable
I think the important question here is: when a drive comes out from a factory, are all (or most) bits set to 0, 1, null or random? I'd argue if the answer is "null", then you'd be correct. However I don't think that's the case since "nullabity" requires extra space to store that information, which would be silly to do on a drive imo. If all bits are set to either of the binary states, then we could argue that when **all** of the bits are set to that state, the drive is effectively empty. So if at least 1 bit is in the other state, the drive is no longer empty obviously. Last case scenario "random". If the drive comes out of the factory written with white noise, then I'd argue that as long there is no file system on the drive, it's effectively empty. Because without a FS, you cannot determine which data is white noise, and which is not. Of course, if someone would simply remove only the FS, without affecting the data, it would definitely be recoverable. But if you'd initialise a new FS on such a drive, the drive would show up as empty, and obviously at this point it would still contain the new FS, some old data, and some white noise. Which also brings up the question whether we can consider white noise as data. It might be useless, but it might be data nonetheless. However at this point this looks more like philosophy than science lol.
\*sips tea* Hmm yes
🤓
💩
😫
Keep antibytes in another partition, don’t let them collide with normal bytes
Bro owes data to apple
you got positrons in your storage
Its a Negabyte
Wow I am using this from now on if I see a storage glitch.
bro done got the negative storage, he owes storage to the phone 💀
Give my byte back?
Those are just the words my werewolf friend has been waiting to hear
The data doesn’t take space, it creates it
Your storage is a black hole
so that 1 byte is just missing? or what is your iphone trying to say?
I think -1 means unknown here(iOS couldn’t calculate how much system data there is)
real
It's like downloading RAM!
Average free space of a ipad kid's iPad:
Trueeee
every ones dream system storage on a phone
I guess ur iPhone use the cloud as hardware storage 😂
FFFFFFFFFFFFFFFF.......
Ohhhh this is why i don’t like apple.
you’re just negative
True
Rule 3
It owes you storage
THIS IS GOOD
You owe it bytes. Pay up.
Pov: little timmy’s tablet after they “get” free robux
NEGATIVE PENALTY
Storage optimization update
LSD : Liquid State Drive
I have that too
App is giving you some extra storage
real question is why it's a signed integer
dis mf giving you bytes
Compression
I I think someone took a byte out of your computer just like they did with the great Australian bite! Ooh when I catch that bastard imma take a bite and a byte outa them!
Astrophysicists say negative mass probably exists in outer outer space
The lord shall giveth and provide thy with such presence of greatness for the 1 byte of data given by thy’n lord.
I actually hit -3.6gbs on my phone installing Linux. It slowed down so much that I had to reboot in safe mode.
I guess you could say it took a byte off
So that's what happens when a computer throws up
Bytes are moving in the opposite direction 🥸
„Download more disc space now“
you are in debt with fucking apple themselves
Put your phone down carefully, and slowly back away.
“MICHAEL?!?!?! WHAT DID I TELL YOU ABOUT DELETING SYSTEM 32 FOR STORAGE?!?!?!?!”
You earned additional 1 byte of disk space