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.
Permalink for comment 535105
To read all comments associated with this story, please click here.
RE[5]: seriously?
by moondevil on Fri 14th Sep 2012 20:27 UTC in reply to "RE[4]: seriously?"
moondevil
Member since:
2005-07-08

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

How many devices have you tried it on?

Actually you might find this talk interesting,
http://vimeo.com/43529195


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

In Android's case JNI is an issue, but not as much as with Mono.

See Andreia's talk, there are some exposed APIs that go multiple times between VMs.

In iOS there is no marshalling happening.

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


In Germany, the only person I've seen carrying a WP7 mobile outside a store, was a guy I've met that works for a startup that develops WP7 games.

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.


Don't take it wrongly. Personally my only issue is that Mono/C# is promoted as the only way to achieve portability of native application across mobile platforms, when actually other solutions do exist, depending on what platforms are valuable to target.

Reply Parent Score: 3