1,192 karma · joined May 4, 2007
1. Preventing / curing all causes of pain. 2. Changing how the body responds to pain.
I think problem number 2 is easier to solve. The human body is a biological machine and I hink we will find better ways of handling pain than today. An example could be an implant in the brain that simply blocks the impulses.
Here's the version I found in the Google cache:
http://webcache.googleusercontent.com/search?q=cache:Jxv6vFH...
You can right click the text and select "Go to web address". It's quicker in my opinion.
What I am missing is a way to see the full picture. That would help place some of the more difficult pieces.
I found something here: http://doom.wikia.com/wiki/Duke_Nukem_3D
"While Doom and Duke Nukem 3D feature similar technology, Duke Nukem 3D could in most respects be considered technically superior. The player can jump, crouch, and aim up or down. The rendering engine features slopes, overlapping and moving sectors, arbitrary scaling of textures and strong scripting capabilities"
The problem is caused by him comparing objects as if they were primitives. The Integer class is basically just a wrapper around an "int" primitive. When an Integer object is initialized with a value between -128 and 127 it will return an object from an internal cache.
The second time he creates an Integer with the value of 127 it uses the cached object, which of course is identical to the previous one. When he tries this with 128, the cache is not used and a new Integer object is created.
tl;dr; Integer is an object where some values are cached to avoid creating a new object. The "==" operator compares the objects, and not the values they represent.
Opera Mini already does this I think.