Geek Jokes

[JonRB]

[clonmult]

james_tigerwoods said:

Mr Will said:

plasticpig said:

mrmr96 said:

james_tigerwoods said:

(I do, tragically, have a vague idea as to why it the copying time changes)

I thought it was because it bases it's time estimate on the number of files left vs. number copied, whereas it would be more accurate if it measured on file size, not number? Am I close?

Nope. The main problem is that other applications and services require access to the hard drive and memory at the same time. There is no mechanism for predict the amount of access these other things require.

The main problem is that it bases the estimated time on the current speed, leading to wild spikes, rather than basing it on the speed over the last few minutes/transfer so far which would smooth it out significantly.

Nope. You're all wrong. It's the Microsoft Randomizer tool that you've left enabled - to disable it you need to ... Shhh, it's a secret ...

Its either the randomiser or just plain bad coding. Bad coding seems more likely.

[ZesPak]

Mr Will said:

plasticpig said:

mrmr96 said:

james_tigerwoods said:

(I do, tragically, have a vague idea as to why it the copying time changes)

I thought it was because it bases it's time estimate on the number of files left vs. number copied, whereas it would be more accurate if it measured on file size, not number? Am I close?

Nope. The main problem is that other applications and services require access to the hard drive and memory at the same time. There is no mechanism for predict the amount of access these other things require.

The main problem is that it bases the estimated time on the current speed, leading to wild spikes, rather than basing it on the speed over the last few minutes/transfer so far which would smooth it out significantly.

Instead of taking average transfer speed, which would take a while to "stabilize", it takes the current transfer speed, which could jump up and down every couple of seconds.

They fixed this for a big part in Win 7, it's much less "twitchy" in 7 ime.

[Mr Will]

clonmult said:

Its either the randomiser or just plain bad coding. Bad coding seems more likely.

Exactly.

Never attribute to malice that which can be sufficiently explained by incompetence.

[hesnotthemessiah]

ASCII to ASCII

DOS to DOS

[marshalla]

A biologist, a chemist, and a physicist are travelling along, and they come across the Pacific ocean. Neither of the three have ever seen an ocean before, and they all get excited to begin experimenting immediately.

The physicist runs up to the water, yells, "I must study the waves in this body of water," drowns, and dies.

The biologist runs up into the water yelling: "I wonder what wildlife must live in the sea!" He, too, drowns and dies.

The chemist takes a moments, and then pulls out a paper and starts jotting things down, mumbling "Ah-ha! Biologists and physicists are solluble in Oceans..."

[spyder dryver]

Not a joke, strictly speaking, but geeky nonetheless...

[plg]

spyder dryver said:

Not a joke, strictly speaking, but geeky nonetheless...

Dman. I don't get many of those...

Is there a maths guru about?

I'll start with the easy one of 8 being 1000 binary for 8.

Edited by plg on Monday 24th January 19:22

[havoc]

plg said:

spyder dryver said:

Not a joke, strictly speaking, but geeky nonetheless...

Dman. I don't get many of those...

Is there a maths guru about?

I'll start with the easy one of 8 being 1000 binary for 8.

1) Don't know.
2) Sum with-reference-to-i (where i goes from 1 to infinity) of 1 divided by 2-to-the-power-i
3) ??? IT?
4) 2 to the power -1, modulo-7
5) Expansion of that operation - 4-phi-squared minus 4-phi plus one. Where phi is the golden ratio and phi-squared minus phi minus 1 = 0. VERY maths-geeky.
6) 3 factorial
7) 6.9999999...(recurring to infinity)
8) Binary notation (stylised)
9) I should know this and I've forgotten what it stands for...
10) Matrix-operator notation - 5x2, essentially
11) ???
12) cube-root of 1728 (i.e. 12x12x12)

[JonRB]

11 is hexadecimal - in C, C++ and similar, "0x" means the number is in hex.

and 9 is 21 in base 4, expressed in mathematical notation rather than computer notation.

Edited by JonRB on Monday 24th January 19:52

[marshalla]

3 is ASCII character written in Hex - 33 (base 16) = 51 (base 10) = "3" (ASCII)

[james_tigerwoods]

spyder dryver said:

Not a joke, strictly speaking, but geeky nonetheless...

I genuinely want that - can I buy it somewhere?

[tribbles]

havoc said:

plg said:

spyder dryver said:

Not a joke, strictly speaking, but geeky nonetheless...

Dman. I don't get many of those...

Is there a maths guru about?

I'll start with the easy one of 8 being 1000 binary for 8.

1) Don't know.
2) Sum with-reference-to-i (where i goes from 1 to infinity) of 1 divided by 2-to-the-power-i
3) ??? IT?
4) 2 to the power -1, modulo-7
5) Expansion of that operation - 4-phi-squared minus 4-phi plus one. Where phi is the golden ratio and phi-squared minus phi minus 1 = 0. VERY maths-geeky.
6) 3 factorial
7) 6.9999999...(recurring to infinity)
8) Binary notation (stylised)
9) I should know this and I've forgotten what it stands for...
10) Matrix-operator notation - 5x2, essentially
11) ???
12) cube-root of 1728 (i.e. 12x12x12)

3) - ASCII for the character "3" - ETA: Well, actually the XML encoding for the "3" character (in hex).
9) - 21 in base 4
11) - Hexadecimal of 11

Edited by tribbles on Monday 24th January 22:37

[Cotty]

marshalla said:

3 is ASCII character written in Hex - 33 (base 16) = 51 (base 10) = "3" (ASCII)

Errr

[fomb]

ZesPak said:

Mr Will said:

plasticpig said:

mrmr96 said:

james_tigerwoods said:

(I do, tragically, have a vague idea as to why it the copying time changes)

I thought it was because it bases it's time estimate on the number of files left vs. number copied, whereas it would be more accurate if it measured on file size, not number? Am I close?

Nope. The main problem is that other applications and services require access to the hard drive and memory at the same time. There is no mechanism for predict the amount of access these other things require.

The main problem is that it bases the estimated time on the current speed, leading to wild spikes, rather than basing it on the speed over the last few minutes/transfer so far which would smooth it out significantly.

Instead of taking average transfer speed, which would take a while to "stabilize", it takes the current transfer speed, which could jump up and down every couple of seconds.

They fixed this for a big part in Win 7, it's much less "twitchy" in 7 ime.

I read up on this a few years back. In essence the system counted the number of files to copy, and the size of the current file. It then assumed all the files were the same size and calculated the total time to transfer at the current speed. This resulted in a crappy number as speed changed, and the current file size changed.

Try copying a a gigabyte file, and a few hundred 1K text files, and you'll see it at it's best

[K50 DEL]

james_tigerwoods said:

spyder dryver said:

Not a joke, strictly speaking, but geeky nonetheless...

I genuinely want that - can I buy it somewhere?

You can indeed.....

$25 from here:

http://www.uncommongoods.com/product/geek-clock?so...

[JonRB]

JonRB said:

11 is hexadecimal - in C, C++ and similar, "0x" means the number is in hex.

and 9 is 21 in base 4, expressed in mathematical notation rather than computer notation.

tribbles said:

9) - 21 in base 4
11) - Hexadecimal of 11

Thanks for the contribution.

[marshalla]

Cotty said:

marshalla said:

3 is ASCII character written in Hex - 33 (base 16) = 51 (base 10) = "3" (ASCII)

Errr

I know. I know.

Girls scare me and even Sheldon Cooper accused me of being a nerd.

[tribbles]

JonRB said:

JonRB said:

11 is hexadecimal - in C, C++ and similar, "0x" means the number is in hex.

and 9 is 21 in base 4, expressed in mathematical notation rather than computer notation.

tribbles said:

9) - 21 in base 4
11) - Hexadecimal of 11

Thanks for the contribution.

Any time you want me to repeat something, just ask

although you didn't do the XML encoding of "3" though

[Cock Womble 7]