Slashdot Mirror
SanDisk Releases 512GB SD Card
Lucas123 writes: SanDisk has announced the world's highest capacity SD card, a 512GB model that represents a 1,000-fold increase over the company's first 512MB card that it shipped a decade ago. The SanDisk Extreme PRO SDXC UHS-I memory card has a max read/write rate of 95MB/s and 90MB/s, respectively. The card is rated to function in temperatures from -13 to 185 degrees Fahrenheit. The 512GB model retails for $800. The card also comes in 128GB and 256GB capacities.
Only if you use the newfangled redefinitions. A traditional GB is identical to a GiB.
The OP is correct. Memory is always expressed in GiB. There is no such thing as Base-10 memory.
So the highest MP camera I could find in a normal store is 40 Mpix (Pentax 645D) * 14 bit RAW = 70MB/picture. So good for 70,000+ photos. Or the Panasonic HC-X1000 4K/24 & UHD/60p camera just released, 150 Mbps = 7-8 hours continuous recording. But I suppose it's good for when you want to carry 10 BluRays in your phone. Whoops, wrong format not microSDXC. I guess there's a niche for this since they made it, but I kinda fail to see the target market, unless it's the "give me the biggest and best you got" crowd.
Live today, because you never know what tomorrow brings
Correctness not an issue; you merely have difficulty with common usage, common sense and ability to relate to normal humans, is all.
For everybody living out the the Bahamas, Palau, the USA, Belize and the Cayman Islands who struggle with the odd Imperial system, the temperature range of this SD card is between -25C and 85C.
http://en.wikipedia.org/wiki/Kilobyte says:
and
Note the difference: kB vs KB.
Celsius is arbitrary too. There is nothing inherently connecting temperature and water.
Kelvin is the only scale based on something fundamental.
Fahrenheit is based on the coldest you can get brine before it freezes and the approximate human body temperature. Both of these make great sense for telling the weather as 0 is dangerously cold and 100 is dangerously hot.
One might argue that a lot of people don't live in the temperate zone where 0 and 100 occur regularly but C's water boiling and freezing points are only good for people at sea level and no one's weather on Earth ever involves boiling water.
"0 is very cold,"
If we are talking Fahrenheit , 0 is nighttime in winter.
"100 is you"
You must be coming down with the flu or something. 98.4 is normal
"200 is boiling water"
On a mountain I spose. its 212 at sea level.
It takes a long time to compute the size of 20 files when a division by 1000 takes 300 odd cycles on a 10kHz machine.
Sorry, man. Division by 1000 isn't even remotely a 300-cycle operation. If you're dividing by 1000 a lot, you're going to multiply by the reciprocal of 1000 instead of doing division. For 16-bit arithmetic, we're talking 6 single-bits shifts and 1 addition, worst case.
It takes a long time to compute the size of 20 files when a division by 1000 takes 300 odd cycles on a 10kHz machine. It doesn't take such a long time when a right shift 10 takes 1 cycle.
This must be the most clueless post about the 1000/1024 divide so far. It never had anything to do with the computer's performance, it's that when you build a digital computer a lot of things will be sizes of two because what you can address with n bytes will be 2^n. Physical memory, memory pages, caches, buffers, floppy and hard drive sectors all the "microunits" in the computer are powers of two. Hint: No actual hard drive gives you 1MB = 1000000 bytes because it's not divisible with 512, in reality they give you 1954*512 = 1000448 so they don't underdeliver. Actually make that divisible by 4096 for modern HDD drives with 4K (no, not 1000) sectors.
There is a single reason why computer scientists usurped the prefix kilo and that is because they needed to describe "one thousand and twenty four bytes" - or multiples of that - very, very often. They needed a shorter name, they never needed the unit "1000 bytes" and so "one kilobyte" became their shorthand for 1024 bytes. And unless you're really good at doing math in your head, tell me how much is seven kilobytes exactly? (And if you answer 7000 I'll slap you). We still say 512GB of RAM. Nobody wants to say 549.755813888 GB of RAM, because multiply that with a billion and you have how many bytes that is. It's not some nice, round number.
Either way you're going to run into some f*cked up conversions if you mix GiB and GB, which I'll use now for clarity. If you have 512GiB of RAM (hey, servers do) and load 512GB from disk, how much of your RAM have you used up? Now while you're calculating that, this other person who uses a GiB system says so that was like ~477 GiB so like ~35 GiB free? Or you have to say you have 549.8 (rounded) GB RAM and use exactly 512 GB. Of course in reality file sizes are probably a rather random size so you'll have two long floating point numbers. At least with base 2 you just have one, because you have exactly 512 GiB RAM.
And when you do have base 2 numbers then multiplication/division gives other nice base 2 numbers like 10 MiB / 2 KiB = 5 KiB. 10.485760 MB / 2.048 KB = how much? It's a lot uglier if you numbers are 2^n values, which again they will be a lot of the time. At least far more often than base 10 as long as you're working with the computer itself and not business data or whatever. If you for example want to make something fit in L3 cache to optimize and algorithm, the numbers will be in base 2. You can't "bugfix" your way out of that.
Live today, because you never know what tomorrow brings
Arbitrary means to pick something at random or at whim. In this case the choice of freezing / boiling points of water were NOT arbitrary, but rather consistent with the rest of the units of the SI system which are based around some interlinking thing.
1L = 1000g of water.
0degC is the freezing point of water.
100degC is the boiling point of water.
1 calorie is the energy needed to heat 1g of water by 1degC (though superseded by an SI unit this was the original metric measurement for energy)
Even if you dismiss this, it's still less arbitrary than a measurement system that bases the arbitrary number of 96degC on the temperature of blood in the human body, and has a zero point where the history is not actually known; is it brine mixed with ammonium chloride with a bit of error added in, was it the coldest day of Fahrenheit's home town? The only thing not arbitrary about the Fahrenheit scale is that it was later redefined ... based around the freezing point of water.
A bit more Wikipedia trivia Celsius was originally called centigrade a completely not arbitrary name meaning 100 steps.
Yes, because your OS incorrectly computes the number of GB. It computes the number of GiB, and then displays GB.
Notably, if you stick that same terabyte drive in a mac, or many linux boxes, it'll register as 1TB.
Kilobyte = 1024 is a standard too, by the way. It's the JEDEC standard for memory sizes.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
RAM generally is, and address space always is.