Linked by Thom Holwerda on Thu 13th Sep 2012 21:44 UTC
General Development "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.
Thread beginning with comment 535031
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Let's face it
by satsujinka on Fri 14th Sep 2012 08:19 UTC in reply to "RE: Let's face it"
satsujinka
Member since:
2010-03-11

Go would certainly be welcome. It would even make a sort of sense.

Reply Parent Score: 2

RE[3]: Let's face it
by moondevil on Fri 14th Sep 2012 11:47 in reply to "RE[2]: Let's face it"
moondevil Member since:
2005-07-08

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.

Reply Parent Score: 2

RE[4]: Let's face it
by satsujinka on Fri 14th Sep 2012 13:48 in reply to "RE[3]: Let's face it"
satsujinka Member since:
2010-03-11

Of course. It is already possible to use Go on Android. The "sorta sensible" part is really just that Go is also a "Google" project. Of course, I don't expect Go to become standard, but after doing some Android dev. I wouldn't mind something a bit less verbose.

Reply Parent Score: 1