Linked by Thom Holwerda on Tue 1st May 2012 21:59 UTC
Mono Project Wow. "One crazy idea that the team had at that dinner was to translate Android's source code to C#. Android would benefit from C# performance features like structures, P/Invoke, real generics and our more mature runtime. [...] We decided it was crazy enough to try. So we started a small skunkworks project with the goal of doing a machine translation of Android from Java to C#. We called this project XobotOS." Most of Android's layouts and controls are now in C#. The small benchmark is stunning, but as much as I admire the work, I'm wondering that this like going from bad to worse - from Oracle's Java to Microsoft's C#.
Thread beginning with comment 516607
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: I'm disappointed
by theuserbl on Tue 1st May 2012 22:43 UTC in reply to "I'm disappointed"
Member since:

The most Android-smartphones have an ARM-CPU. But the last times, there comes some smartphones with x86-CPU.
To run ONE binary on different CPUs, is only possible with VMs (like Dalivik, Java or Mono) or with "universal binaries" (like Apple have done for some time).
The last one blow out the binaries. And if there comes additional CPUs-architectures, the existing programs will not run on it.
So a VM is the only solution!

Reply Parent Score: 6

RE[2]: I'm disappointed
by Alfman on Tue 1st May 2012 23:18 in reply to "RE: I'm disappointed"
Alfman Member since:


As you say, binary portability is an extremely good reason to have a VM, particularly in the mobile device market where there are a large variety of platforms. Compiling to specific individual targets just is not future-proof. Well designed VM's just about completely eliminate problems of locked hardware. Also, new JIT compilers can optimize older programs to use new CPU features.

Another benefit of VMs is applications sandboxing as well as eliminating most memory corruption conditions.

Reply Parent Score: 6

RE[2]: I'm disappointed
by Dasher42 on Wed 2nd May 2012 03:23 in reply to "RE: I'm disappointed"
Dasher42 Member since:

Open source and builds are a solution. As much fragmentation as there is for Android phones, it seems like this problem exists anyway. I'm thinking that virtualizing the processor is a better solution - hence using LLVM and compiling the bytecode to machine code.

Reply Parent Score: 1