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.
Why the hell are we talking about the Fahrenheit scale.
Because the marketing droids who came up with the press release are based in the U.S., the only country next to Birma to use this arbitrary roller-coaster as an official standard.
I'm not a complete idiot... Some parts are missing.
Yes, apparently it is too much to ask that people be correct these days.
The summary clearly states that 512GB of memory is 1000 times more than 512MB of memory, which is patently false. If you're making comparisons, you don't make absolute statements like this. You use qualifying words like "about 1000 times" or "approximately 1000 times" to let the reader know you do not mean to be precise.
Correctness not an issue; you merely have difficulty with common usage, common sense and ability to relate to normal humans, is all.
1/1075th of one LoC, given the numbers in this Wikipedia article and extrapolating from its information:
525 tb + 5 months of 5 tb / month = 550 tb.
(Not counting September as completed, so only April through August.)
Or, you'd need a stack of 1,075 of these SD cards to hold one LoC. (The actual calculation is 1074.21 or so, but you have to round up or truncate off 100 gb of data, and it's the Library of Congress... you can't just throw away 100 gb of data!)
Welcome to the Panopticon. Used to be a prison, now it's your home.
How is 640kb of ram working out for you?
Son, the pixels arent 14-bits each. They are 42 bits each, which is rounded to 48 bits each. 6 bytes per pixel.
"His name was James Damore."
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.
No, a "traditional" GB is the one that was defined way before computer scientists got their hands on it –1000. The 1024 "definition" is actually simply a bug. Engineers working on early machines had a choice – take a bug that pretty much no one would notice on an early machine (because files over 1kB were very rare, much less ones over 1MB), or take a massive perf hit. 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.
Bottom line, early engineers decided a known bug was better than the enormous perf hit of getting it correct. That doesn't mean that what they did is now correct. It means it remains a bug in some OSes.
In Ukraine we have achieving technological dominance again for one time more!
Announcing for world first time, biggest ever microchip. Ability to the processing power of more data is an explosive growth phenomenon.
Now it is Ukraine again the leader!
"Flyin' in just a sweet place,
Never been known to fail..."
http://en.wikipedia.org/wiki/Kilobyte says:
and
Note the difference: kB vs KB.
Well I seem to be both right and wrong, it's 42 bits from the camera but it's losslessly compressed so an actual RAW file is still around 70 MB/photo (listed under cons) so the card does hold 70,000+ photos.
Live today, because you never know what tomorrow brings
"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.
Were you dropped on your head as a child? Quoth the wiki:
Celsius degrees came before Kelvin units.
Dewey, what part of this looks like authorities should be involved?
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.
4K camcorders!
100 units between freezing and boiling is really not that arbitrary.
Peter predicted that you would "deliberately forget" creation 2000 years ago...
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.
SanDisk if you are reading this please make a 512GB Micro SD... thanks!!
Sorry, Dad, you don't know how digital cameras work. Pixels ARE 14 bits each in 14 bit RAW.
In what way do you consider the choice of a measurement which is easily reproducible virtually anywhere worldwide "arbitrary?"
Yes, things like altitude change the scale a bit. Can you can come up with a better solution (very accessible, reasonably accurate, reasonably reproducible) for transfer of a standard temperature scale worldwide with mid-1700's technology? Choosing the freezing and boiling points of water on that basis for something of scientific, industrial and commercial use seems anything but "arbitrary."
"National Security is the chief cause of national insecurity." - Celine's First Law
Really not that much more absurd than setting the coldest temperature based on what a ??? physicist could cool water at a particular height in the atmosphere that changes all the time.
Well, using common core math, maybe.
Gary Dunn
Open Slate Project
Celsius is arbitrary too.
In metric, one millileter of water occupies one cubic centimeter, weighs one gram, and requires one calorie of energy to heat up by one degree celcius - which is exactly one percent of the difference between its freezing point and its boiling point.
In the American system, the answer to "How much energy does it take to boil a room-temperature gallon of water?" is "Go fuck yourself", because the American arbitrary roller-coaster makes it impossible directly relate any of those quantities.
I'm not a complete idiot... Some parts are missing.
The units cancel, so you get 5K er... 5*1024 = 5120.
My favorite solution to the issue is to treat GB, MB, and KB as special units whose meanings are 1024MB, 1024KB, and 1024B, respectively. That's what they've meant for decades, and I'm not going fiddle with giving them two incompatible meanings now. IMO if powers of two don't matter in a particular context, it's cleanest to use Gb, Mb, and kb, SI units referring to 1000Mb, 1000kb, and 1000b (bits), respectively. Bits are a fairly fundamental unit.
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.
Both scales have their advantages and disadvantages. Thing is, most of the world has standardised on Celsius and is easy to convert to scientific units (kelvin).
0C means ice, 100C means boiling. Two common and dangerous points. Most everyday activity falls within that range, and it's easy to tell what something that is 80C is going to be like because it is 80% of boiling water temperature. There really is no reason to stick with Fahrenheit other than tradition.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
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
I think you are mistaken. The equation converting F to C is linear. F = C * 1.8 + 32.0. Both units are completely arbitrary. F used the freezing point of brine while C used the freezing point of pure water as a zero reference. F used the human body temperature and C used the boiling point of pure water as the 100 reference. Arbitrary.
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
RAM generally is, and address space always is.
For most of the world it's easier to use Celsius, like they have for their entire lives. 10 is cold, 20 is nice, 30 is damn hot.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
The new GoPro camera...which hasn't come out yet...is said to effectively capture video at double the rate that it currently does. So it can do 1080p at 120 frames/second.
But there's a problem with that...the existing GoPro, at half that speed, requires the very fastest of SD cards (UHS Speed Class 3) to be able to write the data fast enough. So I was wondering how the hell the camera would even be able to work at 120 fps 1080p resolution in the first place. This card, with its throughput, answers that, since it's triple the UHS Speed Class 3 specification.
For your security, this post has been encrypted with ROT-13, twice.
I have an irrational desire to slap the people who thought inventing GiB was a good idea. I hope it's forgotten eventually. All the justifications for it were (and still are) bullshit -everyone knew what HD vendors were doing and no one who mattered was confused. That's still true , but now I have to explain to people that no, it's not a speech impediment...
Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.