| News | Features | Interviews |
| Blog | Contact | Editorials |
| J2ObjC: a Java to iOS Objective-C translator from Google |
| By Thom Holwerda on 2012-09-13 21:44:00 |
| "We are proud to announce the open source release of J2ObjC, a Google-authored translator that converts Java source code into Objective-C source for iPhone/iPad applications. J2ObjC enables Java code to be part of an iOS application's build, as no editing of the generated files is necessary. The goal is to write an application's non-UI code (such as data access, or application logic) in Java, which can then be shared by Android apps, web apps (using GWT), and iOS." Huh. |
|
| RE[4]: seriously? |
| By zima on 2012-09-14 07:01:00 |
| Well I did put some emphasis on most straightforward there :p (broadly speaking, also how ~XNA is a quite accessible path) |
 - Score: 1 |
| RE[3]: seriously? |
| By moondevil on 2012-09-14 07:09:16 |
|
Using Mono in Android means running two VM alonside each other with lots of marshling between VM, because your .NET application needs to make use of the DalvikVM APIs. Just code the core of your application in C or C++, and make use of the platform native UI for the best user experience. As for WP7, just let it die, as WP8 also supports C++. |
| - Score: 7 |
| Let's face it |
| By ThomasFuhringer on 2012-09-14 07:24:52 |
|
The smartest move would be for Google to move away from Java and switch to ObjC on Android. - I know, just fantasy. |
| - Score: 2 |
| Any GNUstep hope? |
| By fithisux on 2012-09-14 07:56:39 |
| I have non-UI code in java and I would like to make it ObjC, compile it with Gnustep and run. |
| - Score: 2 |
| RE: Let's face it |
| By fithisux on 2012-09-14 07:57:10 |
|
> The smartest move would be for Google to move away from Java and switch to ObjC on Android. - I know, just fantasy. or switch to Google Go. |
| - Score: 4 |
| RE[2]: Let's face it |
| By satsujinka on 2012-09-14 08:19:49 |
| Go would certainly be welcome. It would even make a sort of sense. |
| - Score: 2 |
| Yea, debugging translates code... |
| By dsmogor on 2012-09-14 09:54:50 |
|
is something I just love doing all day long. Edited 2012-09-14 09:55 UTC |
| - Score: 3 |
| RE: Let's face it |
| By Neolander on 2012-09-14 10:31:56 |
|
Actually, I think that interpreted languages sort of make more sense for mobile phones, due to the large amount of SoCs that apps will have to run on. Apple's native code approach only works because there only is a handful of devices to target, with similar underlying hardware. |
| - Score: 4 |
| RE[3]: seriously? |
| By dvhh on 2012-09-14 11:30:05 |
|
Most portable example spacechem Linux (!) Windows Mac iPad Android Tablets Build on mono (While I agree that the game is not graphic intensive, it is a great example for game with mono ) |
| - Score: 2 |
| RE[3]: Let's face it |
| By moondevil on 2012-09-14 11:47:31 |
|
Except that Go does not seem to be that used by Google. It is only part of Google App Engine, because the Go team is doing this work, not the Google App Engine team. For me it appears to be a political decision not to support Go on Android, since the Go team has Go builds for Android. |
| - Score: 2 |
| News | Features | Interviews |
| Blog | Contact | Editorials |