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 535003
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: seriously?
by Nelson on Fri 14th Sep 2012 03:29 UTC 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[4]: seriously?
by Nelson on Fri 14th Sep 2012 16:59 in reply to "RE[3]: seriously?"
Nelson Member since:
2005-11-29

VM alonside each other with lots of marshling between VM, because your .NET application needs to make use of the DalvikVM APIs.


Have you actually used it and run into these supposed performance problems? Ive used it, and I haven't.



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


Yeah, no. To do that, you'd still need JNI on Android, and a Cocoa bride on iOS since key APIs are not available as native interfaces.

You're doing the same bridging that Mono does, albeit without the slight double GC perf impact.

Also, nice little pot shot at WP7, but it has over 100,000 apps, and moving forward, C# will still be the majority language (as it is for Windows 8 apps).

Seriously, I don't get the Mono and C# bashing. Sure, maybe if you felt like hurting your productivity enough, you could use C++, but Mono has been proven to work in the real world.

Reply Parent Score: 2

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[4]: seriously?
by Nelson on Fri 14th Sep 2012 17:00 in reply to "RE[3]: seriously?"
Nelson Member since:
2005-11-29

Im pretty sure you know how to read.

Reply Parent Score: 2