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 516788
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why not just use gcj
by Rugxulo on Wed 2nd May 2012 20:12 UTC in reply to "Why not just use gcj"
Member since:

At least then you bypass the interpretation layer and get a real executable to directly run applications.

Dunno, but (without having tried) it "seems" that only C/C++ are supported via NDK on Android. So maybe GCJ isn't supported there (and I'm honestly not sure it's still maintained upstream much, if at all, though I could be wrong).

Reply Parent Score: 1

RE[2]: Why not just use gcj
by moondevil on Thu 3rd May 2012 15:18 in reply to "RE: Why not just use gcj"
moondevil Member since:

Sadly, GCJ seems to be in a kind of maintenance mode.

Since OpenJDK was made available, the contributions to GCJ development dropped to almost zero.

Reply Parent Score: 2