Why are Microsoft so arrogant?
Why can't they comply with standards?
Why are Microsoft so arrogant?
Other urls found in this thread:
blogs.msdn.microsoft.com
en.wikipedia.org
en.wikipedia.org
twitter.com
Microsoft has no standard
Because they cater to normies who frankly don't give a fuck about our nerd shit.
Probably because someone in charge at the time was old and autistic and now there's a house of spaghetti built on top of it so they can't change it.
Says the faggot who had no idea about standards.
does 1024 meters = km?
no?
then why use 1024 B = kB
Is this serious or bait? It's hard to grasp these days.
One word, BINARY.
so?
when you dominate a market/industry you are the standard
>dec: 10 ^ 3 = 1000
>bin: 10 ^ 3 = 8
hence: 8 bit = 1kbit. faggot.
because they are right
Because when you buy storage it's advertised kilobytes.
so they add 24? is it an older system like metric and imperial?
>then why use 1024 B = kB
You don't, that's wrong. Everybody except Microsoft uses 1024 B = KiB.
Lol, what a dumbass
Microsoft measures file/disk sizes in kibibytes, (which are 1024 bytes) and the displays them on screen as KB (suggesting kilobytes). This results in that thing where you buy a drive and it appears significantly smaller than it did on the packaging.
...
This is the state of Sup Forums, 20 year old's with no clue.
And just to clarify, this whole kibibytes thing exists in the first place because it's a far more useful way to divide up memory for fast processor operation, it lets you do multiplication, division (and I think modulo operations?) by other powers of two by just bit-shifting (which is far easier in hardware than actual multiplication or division).
you can't even into math enough to make a good joke
retard
Because they're a private company and can name their shit however they like
>KiB
the fuck outta here with that gay shit
>being unambiguous is gay
Are there still retards on Sup Forums who don't know the difference between kB and KiB? kB stands for Kilobyte, which is 1000 bytes. KiB is Kibibyte, which is 1024 bytes. Kilobyte, Megabyte and Gigabyte grows by 1000, while Kibibyte, Mebibyte and Gibibyte grow by 1024.
>coming in after the fact to assign the metric system in a place it doesn't belong
>using base 10 for binary
kids these days
Yeah that sounds like kilobytes all right.
Why do people always try to bring "binary" into these discussions? It doesn't have the tiniest shred of relevance to the topic.
>haha le xkdc comik funny make my reddit feel smart xddd
>he he im too cool for le xkcd because i found 4chen :^))))) haha fuk reddit guys!
Holy shit
The current state of nu-Sup Forums what the flipping fuck
I bet you are female
Did you mean to reply to
by any chance?
Fuck off with your nu-Sup Forums meme in every fucking thread, it's getting old.
yes sorry
>burgers trying to look good in math
heh
why youre still using imperical system
because you cant calculate simple math
cant even calculate binary
still
1024 byte = 1 kB
only shit hdd manufacturers popularize 1000 kB = 1000 byte cuz theyre jews
>1024 byte = 1 kB
>only shit hdd manufacturers popularize 1000 kB = 1000 byte cuz theyre jews
Except they're correct and you're wrong: en.wikipedia.org
You're thinking of: en.wikipedia.org
Which nobody claims is 1000 bytes.
>buy 20TB of storage
>lose 10% because reasons
Literally every manufacturer that uses RAM uses JEDEC standards.
Most websites use jedec like Sup Forums and every file hoster.
microsoft stronk
Windows is the ultimate legacy system
Is the imaginary kilobyte one real? I can't tell.
kibibyte was made up after the fact by HDD manufacturers so they could advertise more space than they actually put in the drive.
Kilobyte was originally 1024, and should remain as such since that's how computers actually split up the addressing internally.
digits confirm
Fuck off underage b&
>"If Explorer were to switch to the term kibibyte, it would merely be showing users information in a form they cannot understand, and for what purpose? So you can feel superior because you know what that term means and other people don't."
Holy shit the absolute cope
>Operating system full of legacy spaghetti code that noone understands
>Incorrect usage of KB so deep within the system you realise that even if you did know how to change it you'd completely fuck everything up
>"It's n-not our problem haha, you obviously just have a superiority complex"
classic americans
this is why theyre stubborn to change their imperial system
JEDEC is simple, logical and way superior
1024 byte = kilobyte
1024 kilobyte = megabyte
its a shit mess if you gonna calculate your 1000byte=kB system in octal or binary
>this is why theyre stubborn to change their imperial system
No, the trillions of dollars worth of everything built using Imperial is much more relevant. EUrofaggia and Nipland were repartitioned and formatted by war so starting fresh was easy.
>kilo
>one thousand
>kilometre
>one thousand meters
>kilogram
>one thousand grams
>kilohertz
>one thousand hertz
>kilojoule
>one thousand joules
>kilobyte
>one thousand and twenty four bytes
>simple, logical and way superior
Really actives the almonds
because bytes are 8 bits, and are handled in base 2 or base 16 too, retard.
>and should remain as such since that's how computers actually split up the addressing internally.
Why is this relevant? It's all well and good that files are stored in a sequence of 4KiB or 0.5KiB blocks on a harddisk, but when displaying a size to a user, it should be in a notation that is convenient for a user. Which is powers of 10, not powers of 2.
Say I have a file that is 2501748593 bytes long. This will be stored on disk on 4886228 512-byte sectors, which is not particularly interesting to me as a user, and neither is it particularly interesting to the operating system. We could render this as 2.50 GB, or as 2.32 GiB.
What in the world would the advantage of the latter notation be, here? For me as a user, writing 2.50 GB is more convenient, as that's a number I can gauge relative to my 1.5 TB disk, much better than I could gauge (say) a 75 MiB file against a 1 TiB disk. The actual computer doesn't give a single fuck what notation I use, as to the operating system the file is simply 2501748593 bytes and 4886228 sectors long, and no rounding is involved except for user displays; and I can assure you your file manager doesn't have any preferences about what rounding to use.
From a user interface point of view, the roundness in terms of powers-of-2 is irrelevant, and the computer doesn't care. So why not keep to powers-of-10 and make things convenient for the user? For the user, myself included, 10 * 100 GB = 1000 GB = 1 TB is convenient, and 10 * 100 GiB = 1000 GiB = 0.9766 TiB is a stupid gotcha.
/thread
And what does that have to do with rounding to powers of 1024 versus powers of 1000?
Binary representation > your feeble need for consistency across all fields. A byte was designed and conceived on a base-two system, a base-two system it remains. Bytes aren't distances or weights.
so why don't you use KB/MB/GB units on your computer? Don't use KiB, MiB, or GiB you moron.
kek
u stupid shit
>Binary = 01111111111 ; Decimal = 1023
>Binary = 10000000000 ; Decimal = 1024
way more simple, easier, superior and logical way to do it
>it should be in a notation that is convenient for a user. Which is powers of 10, not powers of 2.
Then why do freetards still use power of 2 units?
this has to be bait
>10 * 100 GB = 1000 GB = 1 TB is convenient, and 10 * 100 GiB = 1000 GiB = 0.9766 TiB is a stupid gotcha
This is true
and makes programming easier
this kibishit is for brainlets that cant understand computer language.
>K-bar
>/K/ilobyte
>7.62*39 bytes
>slavshit a best
Sorry for the digression
How fucking braindead are you?
They only way that could every be easier is if you're using some high level shit like python or lua.
If you're doing anything on a low level then 1024 absolutely makes more sense.
> 10 * 100 GB = 1000 GB = 1 TB is convenient
Enjoy being jewed for 92 gigs!
...Oh wait, you do.
>1000 should mean 1024
No. The prefixes were used incorrectly and HDD manufacturers used proper units that are more fit for human use.
...
I'm not sure if it's even possible to get this across to you, but the fact that bytes store data in base-two, does not IN ANY WAY mean that we should talk about a *number of bytes* in base-two.
When I am ordering a set of fifty green pens, I don't have to write *the order* in green ink, because I am talking about green pens. I just use whatever ink and pen is convenient, for the order. And likewise, when I talk about a number of bytes, I still write that number in notation systems that are convenient for numbers. Which involve powers of ten, not powers of two.
...
What a dogshit analogy.
Windows just reads it as base 1024, instead of base 1000. You lost nothing.
>buy 20TB of storage
>lose 10% because HDD manufacturers are jews who didn't pack the drive with proper terabytes
>buy 20TB of storage
>windows calls it 18TB, despite the disk actually containing 20TB, because of reasons
>whine at the harddisk manufacturer
no
>Literally over 20TB
>Winfags will still complain about this
2¢ have been deposited in your Seagate™ account.
Microsoft has always liked to do everything their own way and try to force the markets to follow
>literally use metric prefixes
>metric doesn't belong!!
brainlet
A brainlet's guide?
Seems like a joke aimed at retards
But it was the HDD manufacturers that forced the kb = 1000 bytes meme.
>well established metric standard
>meme
They really went from Cyclone V to Cyclone 10?
Yes, which was then used by computers, which don't operate in base 10.
It's not that hard to read in context user.
No, the analogy is quite apt. It's just the underlying ideas that are retarded, which the accurate analogy brings to light.
How about drive makers start selling 20 TiB drives instead of 20 TB drives?
I imagine that if there is demand, they will do exactly that. I also imagine that there isn't a single bit of demand.
Then went from MAX-II to 10
>kilo always means exactly 1000
>apart from when talking about computers because memory is in groups of 1024 lol
Ah, now I get it.
I'm just going to go down to the shops and pick up a kiloegg of eggs (6) and kiloslice loaf of bread (20).
Hopefully my new kilokey of keycaps (104) will have arrived by the time I get back.
You're just being purposefully obtuse, here.
dividing by 10 to go up in measurement is too easy and shows a lack of will and determination
dividing by 12 to convert inches to feet shows a powerful devotion to god and country that nihilistic eurotrash simply cannot fathom
The mouseover is actually the most insightful part of that one: the real reason noone uses kibibyte is, frankly, that it sounds really stupid.
>no demand
t. seagate
/thread
why does anyone genuinely give a shit but autistic nerds desperate for any opportunity to regurgitate trivia nobody cares about
Is OP picture 288 KB or KiB?
Hey reddit, this is a tech sub, we like talking about nerd shit here.
>1024 bytes = 1 "kelvin byte"
What did you mean by this, OP?
Does SI apply to computer shit tho. I knew KB was 1024 not 1000. Even tho k is x1000 normaly
Because they don't want anybody competing within their field you silly. If they followed standards they would lose the competition.
Binary just means base 2.
Kilo means 10^3
In binary 2^3 would be 8
That makes no sense so we use Kibi (kilo binary)
which is 2^10
If you look carefully and use all of your fingers you will notice that neither the base nor the power of Kibi are the same as kilo.
Pretty often I see 1 MB = 1024000 bytes which is fucking hilarious.
How about 1 TwoToTheTen Bytes? Or 1 TwoSquaredSquaredSquaredSquaredSquaredSquaredSquaredSquaredSquaredSquared Bytes?
oh my fucking god.
they are already you dumbfuck, it's windows who labels it as 20tb instead of 20tib.
>Incorrect usage of KB so deep within
Nice to see you have no idea what you're talking about.
Windows uses KiB and the likes for all the data calculations it performs. It just names it as KB and the likes, because that's what people are used to.
That's the reason `1TB" drive will show up as "931GB"
Would it be better for Windows to use proper terminology? Probably.
Is to worth confusing the normies? Evidently not - you're already confused despite pretending to be somewhat computer-literate.