| 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]: Let's face it |
| By satsujinka on 2012-09-14 13:48:43 |
| 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. |
 - Score: 1 |
| RE[3]: seriously? |
| By phoenix on 2012-09-14 15:41:56 |
| 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? |
| - Score: 2 |
| Very cool |
| By pmac on 2012-09-14 15:53:04 |
|
Very cool, but your data access layer would have to be self-written/managed on both platforms. It's obviously not going to translate the Android content provider API, and I don't see how it could work with iOS' CoreData, so you'd have to manually do your DB data reading/writing code, right? That sounds like you'd end up with a horrible Frankenstein app, but I don't know. If Google is using it on some of its iOS apps (would love to know which), there must be a way to do that better. For projects without huge resources, it sounds great. But ideally you'd write each app from scratch. I have no idea why Google would be using this itself. And for all the people talking about MonoTouch: hahahahahaha. Edited 2012-09-14 15:58 UTC |
| - Score: 1 |
| RE[4]: seriously? |
| By Nelson on 2012-09-14 16:59:20 |
|
> 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. |
| - Score: 2 |
| RE[4]: seriously? |
| By Nelson on 2012-09-14 17:00:04 |
| Im pretty sure you know how to read. |
| - Score: 2 |
| RE[2]: Let's face it |
| By Nelson on 2012-09-14 17:01:26 |
| Very true. JIT compilers are good enough, and an intermediary bite code ensures architecture agnosticism |
| - Score: 2 |
| RE[5]: seriously? |
| By moondevil on 2012-09-14 20:27:50 |
|
> > 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. |
| - Score: 3 |
| Comment by kovacm |
| By kovacm on 2012-09-16 10:31:22 |
|
Hm... Google bought Motorola and Motorola bought before 280 North - cappuccino.org "Cappuccino is built on top of standard web technologies like JavaScript, and it implements most of the familiar APIs from GNUstep and Apple's Cocoa frameworks." |
| - Score: 1 |
| News | Features | Interviews |
| Blog | Contact | Editorials |