Why are they still allowed to do this?
j e w sews
>>107667259Tera is metric SI prefix and the drive has 2 000 000 000 000 bytes. It is accurate. It's your OS showing you values divided by 1024 that is wrong. IIRC macs had this fixed years ago.The funny thing is, everyone who learned computing knows of this so it should surprise nobody. The even funnier thing is seeing Amazon 1 star reports on large HDDs that go like "I ordered a 20TB drive but it shows up as a 18TB one, returned it, never buying from this vendor again."
>>107667285>Tera is metricSo it's the fault of the euros again
>>107667259Because you don't know difference between TeraByte and TibiByte
>>107667311>It's the fault of the euros that computers don't work in base 10It's the fault of Microsoft for showing you TiB values with a TB suffix.It's your fault for being so fucking computer illiterate to not know this.Fuck I hate this board.
>>107668544Windows runs the world, you are the cuck that needs to learn about computers.
Use Linux. It's accurate there.
>>107667259Windows shows wrong units
>>107667259>>107667364>Because you don't know difference between TeraByte and TibiByteTrue, but still stupid both formats are used pretty much interchangeably. Your OS and other software should use the same method of displaying filesizes as your HDD/SSD manufacturer. Kilo is a thousand, not 1024.
>>107667285The definition is 8 bit = 1 byte, 1024 byte = 1 KB. The SSD/HDD manufacturers are frauds. They even produce things like 512 fake GB disks so make people believe it's half a TB. >>107668606It says KiB on my machine. That's also OK even though it's actually KB. >>107668620
>>107668620Windows is correct though.
1000 byte KBs = jewish NWO shit1024 byte KBs = as God intended
>>107667285>It's your OS showing you values divided by 1024 that is wrong
>>107668676>>107668687Kilo has been 1000 for over 300 years before Microsoft even existed you stupid kike
>>107668717Forgive them. They are Burgers and real units confuse them.
>>1076686871KB = 6 million bytes as the torah intended>>107668717Not the first time kikes try to increase certain numbers
>>1076687171 KB was 1024 bytes before Microsoft existed, anon. It has nothing to do with your masonic metric horseshit, either
>>107668717This and /thread
>>107667259Personally, I blame jews
>>107667311If it weren't for Euros the drives would use terabytes everywhere in the world but use something like "bWords" for every 4 gigabytes (billion words, word being the highest value a CPU can operate on, in this case 32 bits or 4 bytes.).
>>107668703kilo/mega/giga is value divided by 1000, not 1024. Your OS not following established scientific standards is an objectively wrong choice. But what would you expect from an OS coded by indians using AI?
>>107667259>buy a car>why must I have chairs in it?
>>107667259>buy 4TB SSD>it shows up as 4.1TB Sorry anon, those missing NANDs must have ended up in my drive, kek get fucked
I WANTED TWO BY FOUR
>>107668676>8 bit = 1 byteYou know, that was not always the case. A byte was the smallest addressable memory unit, which depending on the architecture could be anything from 1 bit to 48 bits. The idea of 8 bit = 1 byte only became ubiquitous with the immense success of IBM's System/360 line in the 1960s. There is a word to avoid this ambiguity: 8 bit = 1 octet.
>>107668676on Thunar you can choose what you want to see>MB or MiBI'm guessing all the other file managers should offer something similar
>>107667269sex with that child
My cpu doesn’t run at promised speed in ghz, my disk doesn’t come with promised space, my ram doesn’t come with promised speed and space, what else is not a lies?
>>107667259Some virgin in a lab said "kilo-something" in the 1950s, because 1000 was close enough to 1024, and it stuck because everyone knew what he meant. I love how you "people" try to position yourselves as tech enthusiasts, yet continue to get confused and throw tantrums about this 70 years later.
>>107668958Nah, a byte has always been 8 bits. What you're thinking of is "words" (hence why early computers and storage devices talked about their capacity in "[machine] words") - which yeah, have been some wacky values over the decades. The first mainframe I worked with had 12-bit words, which we called "slabs".
>>107669275this is more of a winbabby thing. they list KiB as KB because DOS did. hard drive manufacturers listed KB as KB for jewish reasons and windows users got confused. linux users also got confused because it lists KiB as K in cli apps and used to list KiB as KB in gui apps before adding in the i in the middle at some point. also KiB vs KB got standardized really late, like the 00's. and only deranged trannies use the real KB for anything. a 1024 byte "kilobyte" was og for decades and nobody wants to say kibibyte because it sounds retarded. linux calling it just K is the saving grace. a K was always 1024 and always will be 1024. but it could mean bit or byte depending if you're an ISP so you're getting jewed by 2 industries. i think neo geo also referred to mbit as mega. anyway normgroids became forced to learn the difference if they were to be correct but they didn't so now we have this thread
>>107667259Because it's not the drive manufacturer's fault that windows gets the numbers wrong.
>>107667285>Tera is metric SI prefix and the drive has 2 000 000 000 000 bytes.I don't remember ever agreeing to this absolute horseshit.
>>107667285But they taught me in school that every bit halves uncertainty, so adding a bit is always 2^N+1 capacity.
