Javascript has closures and functions as first order objects, Java doesn't. Java has classes and inheritance, Javascript doesn't (but you can sort of implement it yourself). They are just completely different languages and need to be treated as such.

The 64-bit linker can link 32-bit object files, albeit without link-time code generation.

Here: http://msdn.microsoft.com/en-us/library/5wy54dk2(v=VS.80).aspx ... However it does not support link-time code generation when you're linking object files in a non-native format.

Ah, sorry -- I see the difference now, you're using link time code generation which the x64 bit linker is not capable of when the machine type is x86.

hello.c:

#include
#include

int main(int argc, char *argv[])
{
    printf("Hello world!\n");
    return EXIT_SUCCESS;
}

hello.bat:

@ECHO OFF
SETLOCAL
CALL "%VS80COMNTOOLS%..\..\vc\vcvarsall.bat" x86
cl /MT /c hello.c
ENDLOCAL
SETLOCAL
CALL "%VS80COMNTOOLS%..\..\vc\vcvarsall.bat" amd64
link /MACHINE:x86 /LIBPATH:"%VCINSTALLDIR%\lib" libcmt.lib hello.obj
ENDLOCAL

output:

C:\Project>hello.bat
Setting environment for using Microsoft Visual Studio 2005 x86 tools.
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86

Copyright (C) Microsoft Corporation. All rights reserved.

hello.c
Setting environment for using Microsoft Visual Studio 2005 x64 tools.
Microsoft (R) Incremental Linker Version 8.00.50727.762
Copyright (C) Microsoft Corporation. All rights reserved.

C:\Project>hello.exe
Hello world!

Here: http://msdn.microsoft.com/en-us/library/5wy54dk2(v=VS.80).aspx

You might want to look into the /Machine:X86 option to the 64-bit linker...

Why can't you use the 64-bit toolchain from VS2005 to produce 32-bit binaries?

Are you dumb? ... You're using the VS2010 IDE to run the _exact same_ linker they are having problems with. How does that solve anything?

You're wrong, you can easily output 32-bit binaries with a 64-bit toolchain with MSVC - even from within the Visual Studio IDE if you set up the environment from the command line and then type "devenv /useenv". However you need to be running a 64-bit Windows which presumably the Firefox buildbots aren't.

The future of rendering in video games has always been evident if you look at high-end rendering for films. If you look at a product like Renderman, ray-tracing is used for specific materials in the scene, but not commonly used for rendering the whole frame. Getting realistic materials out of the renderer is the real problem, not rendering mirror balls.

So, Deepwater Horizon (and hundreds of other smaller disasters, still with larger environmental impact than the Fukushima incident) never happened?

The reality is that nuclear is safer than oil, and yet there is so much fear, It's like airplanes, occasionaly one falls down and people are afraid of flying even though it is 100x safer than driving a car which people do every day without fear.

I'm working in a company that does Scientific Visualization, and we have driver issues on a regular basis and have to find workarounds for them. It's a big pain to do testing with all kinds of different configurations and try to work around the problems in the drivers. The reason you don't have driver issues is because you play games and the poor graphics programmers have had to work around all the issues in the drivers you're running. If you have some combination of driver/graphics card that the developers didn't test, chances are you're going to have issues.