Evan

Kirk: ICAHHHHHHHHN!

Yes, especially how the Zune bug was analyzed by users on the Slashdot article and proven to be a negligent bug in the code(as the relevent block was released to the Internet).

This has nothing to do with the ARM chip in question. If it has a limitation, it's the programmer's fault for not taking it into consideration and working around it.

This is even more confusing when you realize that modern Macs are basically IBM-compatible(wow, haven't used that term in ages) x86 PC's anyway. Companies need to advertise that they run on MacOSX or Windows instead of Mac and PC, as if they are two different things.

You son of a bitch.

Pre-rendered in-game screenshots? Does that even make sense?

Halo 2 working on XP was easily done because it arbitrarily required DirectX 10 but didn't use any of it.

It is a compatibility layer in the sense that it re-implements DirectX to just forward to other system libraries. Direct3D calls for example are handled, then passed to the OpenGL library as OpenGL calls.

The compatibility layer introduces a small performance hit, but not really much. In this case, the conversion is done by taking the source code of the game, and implementing the compatibility at compile-time, so the calls aren't necessarily always converted at run-time. It would be essentially a program that runs on OSX.

The use of Cider/etc for porting games is a lazy way of doing it instead of re-writing the rendering and input for each platform manually(which would result in a major performance boost), though it does save on development costs.

Cider being based off of Wine would make it *not* an emulator, but rather a compatibility layer. Emulation is when you simulate a hardware environment, which is not what happens here.

GENTLEMEN.

Step 1: Offer more phones with Android.
Step 2: ...
Step 3: Profit!

Invisible chair!