Actually, the grammar seems fine? Or at least I haven't noticed any problems with it. TFA as a whole seems pretty good actually. The file sizes are still incorrect, though; it calls the units kilobytes now, but it still claims there's 262 of them.

The seven blocks at the start would make it 263 KB, but I don't think that what you meant.

>The file sizes are still incorrect, though; it calls the units kilobytes now, but it still claims there's 262 of them.

1024 * 1024 / 4 B = 262144 B = 262.144 KB = 256 KiB

Yes, exactly; 262144 bytes is 256 kilobytes.

262144 bytes; 262144 / 1024 = 256 kibibytes

262144 bytes; 262144 / 1000 ≈ 262 kilobytes

KB is kilobyte. KiB is kibibyte.

> kibibyte

I wonder if anyone uses this abomination of a word in real life though.

Not that I know of; they're called kilobytes.

Yes, KB = kilobyte = 1024 byte.

At this point I can only assume I'm being trolled.

This whole thread is confusing to me as well. Isn't the whole point of a kibibyte to work in increments of 1024, unlike kilo, which is actually 1000, as defined by the sciences long ago?

So 1024 * 256 is 256 KiB by definition, since a Kibibyte is literally 1024 bytes, and the number of Kilobytes will by higher, since the number it represents is smaller.

Either user a1369209993 is unaware of the distinction ( https://en.wikipedia.org/wiki/Kibibyte ) or then they are deliberately ignoring it (My guess: to defend the old definition of kilobyte = 1024 bytes) to the point that their messages look like trolling.

Reality will forcibly catch up with them when they try to buy a new harddrive.

That's what I thought. I really only care about how much "stuff" I can store in a block, which is 1,024 bytes. If that's 1KiB or 1.024KBs, the distinction isn't worth that much brainpower.