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 534996
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: seriously?
by darknexus on Fri 14th Sep 2012 02:58 UTC in reply to "seriously?"
darknexus
Member since:
2008-07-15

Just use Mono with MonoTouch and MonoDroid

What, and add a bunch of bloat to my app? No thanks. The default system APIs can already add enough of that and, especially in the case of Android apps, they really don't need to be any slower. Write once, run everywhere doesn't really work as well as most people seem to think.

Reply Parent Score: 1

RE[2]: seriously?
by Nelson on Fri 14th Sep 2012 03:29 in reply to "RE: seriously?"
Nelson Member since:
2005-11-29

What bloat? Size? Performance? I've found it adds a few MBs to size, but performance isn't really severely impacted.

Start up? Slightly, but you can get around that in well documented ways.

The upside? The Mono JIT is dramatically FASTER than Dalvik. So, no, actually, if anything it makes your app more responsive.

Plus, write once run anywhere was never the intention. The intention is code sharing. Write platform agnostic back end code and write a native front end for Android, iOS, Windows Phone, Windows 8, WPF, and OSX (MonoMac or Silverlight)

.NET is the only platform enabling actual, real world, non made up, cross platform developer productivity.

It'd help if you tried it once in a while.

Reply Parent Score: 4

RE[3]: seriously?
by moondevil on Fri 14th Sep 2012 07:09 in reply to "RE[2]: seriously?"
moondevil Member since:
2005-07-08

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++.

Reply Parent Score: 7

RE[3]: seriously?
by phoenix on Fri 14th Sep 2012 15:41 in reply to "RE[2]: seriously?"
phoenix Member since:
2005-07-11

So, how is a "faster VM than Dalvik" relevant to a technology for writing apps on iOS devices using a Java-to-Obj-C translator?

Reply Parent Score: 2

RE[2]: seriously?
by zima on Fri 14th Sep 2012 05:42 in reply to "RE: seriously?"
zima Member since:
2005-07-06

>Just use Mono with MonoTouch and MonoDroid
What, and add a bunch of bloat to my app? No thanks. The default system APIs can already add enough of that and, especially in the case of Android apps, they really don't need to be any slower. Write once, run everywhere doesn't really work as well as most people seem to think.

Meanwhile & pushing aside prejudices, the facts seem to be that ~Mono is the way which quite possibly gives most straightforward multi-platform capabilities with nice performance (adequate for that most demanding category: games), and numerous multi-platform examples in appstores - some of them quite high-profile (Bastion, for example - Xbox, Windows, iOS, OSX, Linux Humble Bundle)

http://monogame.codeplex.com/

Edited 2012-09-14 05:48 UTC

Reply Parent Score: 2

RE[3]: seriously?
by moondevil on Fri 14th Sep 2012 06:52 in reply to "RE[2]: seriously?"
moondevil Member since:
2005-07-08

And I thought that would be C and C++.

Reply Parent Score: 3

RE[3]: seriously?
by dvhh on Fri 14th Sep 2012 11:30 in reply to "RE[2]: seriously?"
dvhh Member since:
2006-03-20

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 )

Reply Parent Score: 2