It's not about what consumer needs 64 bit for today's applications... it's tomorrow's applications. First there must be a base of users out there.
Do you remember the opportunity brought about by the 386? Who needed that when all the modern applications ran fine with the 286? The 386 even broke some of the old 286 code. But it was still very useful to programmers who could spend focusing on quality (and bloat?) rather than worrying about how to confine data to 64 K blocks. Almost 20 years later we are still benefitting from the whole flat memory model that finally came to x86 (flat up to 4 GB, that is).
If you have to ask the question of who needs it, then it's not you... yet. Sure the first adopters are the Corporate people who know they need it as well as the "look what I have" crowd. But I'm pretty sure that there will be consumer applications that will make 64 bits necessary after there is enough consumers that have them.
And I bet that he's not going to buy any music now.
At 4 minutes per song, that's... (wait a sec...) over 16 days of nonstop music.
At 75 minutes per CD, that's 320 CDs. At 15 bucks per CD that's $4800 in revenue (or $4500 in profit) that the record company has had stolen from them!
My brother has worked at an independent CD maufacturing plant for 13 years (they used to do tapes). He repairs the duplication machines They handle programs, music CDs, etc. They often make shipments directly to the consumer.
I recently asked him how much they charged to produce a CD today.
He said "18 cents."
I said "No, I mean with the case"
He said "18 cents."
I said "No, I mean with all the inserts and stuff."
The last thing that I want to do is to try to convert between mebibyte and megabyte. I have enough numbers and voices in my head.
The whole purpose of a measureing system is for scale. We know that a kilo*kilo = mega,
mega*kilo = giga. That's good enough.
Forget that it doesn't make a pretty number in
base 10.
It would be just as easy to to get everyone to create a new unit, call it a bite.
One bite = 1.024 byte.
so a kbite = 1000 bites or 1024 bytes.
Forget quantization problems, this is to show that the idea is silly.
Slashdot Mirror
Refer to them as
Monitoring Apex System Taking Reconnaissance (MASTR)
and
System Likely Answering Veraciously (SLAV)
Should be clear enough.
It's not about what consumer needs 64 bit for today's applications... it's tomorrow's applications. First there must be a base of users out there.
Do you remember the opportunity brought about by the 386? Who needed that when all the modern applications ran fine with the 286? The 386 even broke some of the old 286 code. But it was still very useful to programmers who could spend focusing on quality (and bloat?) rather than worrying about how to confine data to 64 K blocks. Almost 20 years later we are still benefitting from the whole flat memory model that finally came to x86 (flat up to 4 GB, that is).
If you have to ask the question of who needs it, then it's not you... yet. Sure the first adopters are the Corporate people who know they need it as well as the "look what I have" crowd. But I'm pretty sure that there will be consumer applications that will make 64 bits necessary after there is enough consumers that have them.
640 TB should be enough for anybody.
Blue tooth enabled drive: $400
Trip to Mac section of computer store: free
Free software while you "pose" around the imacs: Priceless
(of course, it's mac software, so depending on your perspective it could be worthless... your call)
Leave it for the wifey.
:)
She'll flush it.
Tablet 12843 begins: "MAKE MONEY FAST"
Tablet 34935 has:
>>>> me too!
>>>
>>> me too!
>> Me Too
>
> ME TOO
--
I think that four fifths of the tablets are actually "Cuneispam".
And I bet that he's not going to buy any music now.
At 4 minutes per song, that's...
(wait a sec...)
over 16 days of nonstop music.
At 75 minutes per CD, that's 320 CDs.
At 15 bucks per CD that's $4800 in revenue
(or $4500 in profit) that the record company
has had stolen from them!
My brother has worked at an independent CD maufacturing plant for 13 years (they used to do tapes). He repairs the duplication machines
They handle programs, music CDs, etc. They often make shipments directly to the consumer.
I recently asked him how much they charged to produce a CD today.
He said "18 cents."
I said "No, I mean with the case"
He said "18 cents."
I said "No, I mean with all the inserts and stuff."
He said "That's included in the 18 cents."
He wasn't kidding.
Okay, this is what I heard: "blah blah blah, blah blah blah" (the puncuation doesn't help me)
The last thing that I want to do is to try to convert between mebibyte and megabyte. I have enough numbers and voices in my head.
The whole purpose of a measureing system is for scale. We know that a kilo*kilo = mega,
mega*kilo = giga. That's good enough.
Forget that it doesn't make a pretty number in
base 10.
It would be just as easy to to get everyone to create a new unit, call it a bite.
One bite = 1.024 byte.
so a kbite = 1000 bites or 1024 bytes.
Forget quantization problems, this is to show that the idea is silly.