R0b0t1
2007-10-25 15:29:29
Well, this is pretty trivial - but do you think that computer architects will start using 128 bit integers? (This is after 64 bit, or an "Int64").
After 32 there is:
64 bit: 2^64 = 9.223.372.036.854.775.808 (nine quintillion)
128 bit: 2^128 = 3,4028236692093846346337460743177e+38 (dunno)
256 bit: 2^256 = 1,1579208923731619542357098500869e+77 (too large pl0x?)
512 bit: 2^512 = 1,3407807929942597099574024998206e+154 (WTF)
I can't really see the use of any of these but… Well, way back when the dinosaurs walked the earth, they though 1 meg of memory was more than anyone would ever need. What now?
Smartzkid
2007-10-25 15:34:16
Not for a long, long time.
Smartzkid
2007-10-25 19:40:55
:p
Tell me, when do you ever use an integer that's bigger than 32 bits?
Maybe certain scientific applications, but other than that, I can't come up with many uses for anything bigger than 64 bits.
R0b0t1
2007-10-26 15:44:32
The supa dupa noob-inater encryption/auth fantastic service maybe?
Mr.Klean
2007-10-26 17:22:16
Well there was 8-bit and nobody ever thought of the 64 bit of today? I say we will soon get to 1024-bit in about a decade.
R0b0t1
2007-10-27 23:59:41
Holy shit *.*
What would we use that for?
Eicca
2007-11-01 15:36:56
I don't really see, where do you need that big integers o__O
JuKKa
2007-11-01 15:50:52
What would be the point? When would ANYBODY use so big integers?
Or maybe 1024-bit encryption, if anything could handle it? (have fun cracking that one)
Mr.Klean
2007-11-02 16:50:27
From: Kik
Or maybe 1024-bit encryption, if anything could handle it? (have fun cracking that one)
Well if we had 1024-bit encryption we would need very fast computers. I mean as encryptions grew so did the technology meaning it was fast enough to crack it. I don't think we will ever get around cracking, we will just remain lucky not to get cracked, and keep in mind that there is ALWAYS a possibility of getting cracked.
Santa_Clause
2007-11-02 23:15:51
From: R0b0t1
Well, this is pretty trivial - but do you think that computer architects will start using 128 bit integers? (This is after 64 bit, or an "Int64").
After 32 there is:
64 bit: 2^64 = 9.223.372.036.854.775.808 (nine quintillion)
128 bit: 2^128 = 3,4028236692093846346337460743177e+38 (dunno)
256 bit: 2^256 = 1,1579208923731619542357098500869e+77 (too large pl0x?)
512 bit: 2^512 = 1,3407807929942597099574024998206e+154 (WTF)
I can't really see the use of any of these but… Well, way back when the dinosaurs walked the earth, they though 1 meg of memory was more than anyone would ever need. What now?
How much time do you have to waste of your life…? By the way…we could use this to lag our computers…badly.
procedure LagComputer;
var
I : Integer;
begin
for I := 0 to 1000000000000000000000000 do
WriteLn(IntToStr(I));
end;
begin
LagComputer;
end.
Good luck making your computer run after that.
n3ss3s
2007-11-03 06:16:48
Roflmao, how long was the time between making the joke tut and this thread? :p lolled at - "nine quintillion, dunno, too large pl0x, WTF " :D :D :D :D :D
legendaryhero90
2007-11-04 03:14:21
From: Kik
Or maybe 1024-bit encryption, if anything could handle it? (have fun cracking that one)
LMAO i think i would actually! :D
though it might take me a life time….:p
Rikje
2007-11-04 04:06:51
From: Santa_Clause
How much time do you have to waste of your life…? By the way…we could use this to lag our computers…badly.
procedure LagComputer;
var
I : Integer;
begin
for I := 0 to 1000000000000000000000000 do
WriteLn(IntToStr(I));
end;
begin
LagComputer;
end.
Good luck making your computer run after that.
you're scipt:
Successfully compiled
0
Successfully executed
it didn't lagg :p