funny jpg topic

[Crusher]

[PingoSuSE]

secret of the white smoke .... is this weed from your farm Crushy?

[PingoSuSE]

[PingoSuSE]

1. Start video (this is just to have some music in the background)
2. scroll below and read it



Watch this vid @ Youtube (new Window)

Everything u say on wurst servers can and will be used for or against you

superfluous text is removed for easier reading...there's some artistic freedom too

[moon]

omg pingo off the leash

[felixmole]

:lol:

[Image: Pen is broken]

Nice find, the employee who wrote that had a lot of humour

[Crusher]

[Kitekater]

.,.

[natirips]

I didn't think DSL was fast. Actually, I think all the computers in the world altogether are slow*.

*A long and boring story:
I recently considered making a very realistic game/simulation engine in which I'd simply place atoms and simulate physical forces. Of course, you cannot simulate more in-game atoms with a CPU/GPU/whatever consisting of less atoms. So I thought about increasing the size of atoms from 0.000 000 000 1m to 0.001m. That would be 10 000 000x less atoms in a 1D simulation, and 1000 000 000 000 000 000 000x less atoms for a 3D simulation. Sounds like a big simplifications. But, that's still 1 000 000 000 atoms (=1 Giga-atom) per cubic meter of dense simulated matter (i.e. concrete). That times number of bytes per a variable, times the number of variables per atom times number of frames per second** (**if you want to simulate proper collision detection (atoms should usually travel mach less than their size per frame to prevent quantum-tunneling-like effects at low speeds in macroscopic environment) and/or sound (at least 44000fps) you cannot settle down for 30fps) gives a lot of data to process (that only for 1 cubic meter of game-space). Now take a typical game world size into account and you get very much lots of data to process.


On another note: funny how I suddenly understand German when it talks about ejaculation and sperm.

[zietsh]

I didn't think DSL was fast. Actually, I think all the computers in the world altogether are slow*.

*A long and boring story:
I recently considered making a very realistic game/simulation engine in which I'd simply place atoms and simulate physical forces. Of course, you cannot simulate more in-game atoms with a CPU/GPU/whatever consisting of less atoms. So I thought about increasing the size of atoms from 0.000 000 000 1m to 0.001m. That would be 10 000 000x less atoms in a 1D simulation, and 1000 000 000 000 000 000 000x less atoms for a 3D simulation. Sounds like a big simplifications. But, that's still 1 000 000 000 atoms (=1 Giga-atom) per cubic meter of dense simulated matter (i.e. concrete). That times number of bytes per a variable, times the number of variables per atom times number of frames per second** (**if you want to simulate proper collision detection (atoms should usually travel mach less than their size per frame to prevent quantum-tunneling-like effects at low speeds in macroscopic environment) and/or sound (at least 44000fps) you cannot settle down for 30fps) gives a lot of data to process (that only for 1 cubic meter of game-space). Now take a typical game world size into account and you get very much lots of data to process.


On another note: funny how I suddenly understand German when it talks about ejaculation and sperm.

I am hoping for quantum computers