Meego vs Android apps (C or Java?)
Here's something that I can't answer straightforward and it would be nice to have some comments from Nokia on this.
Let's assume that MeeGo is released and that it's awesome. Now, suppose that other vendors start using it for their phones and it becomes an Android-like OS where multiple vendors are using it. Assuming the current way MeeGo is designed, is that possible? Let me explain that: Android apps are written in Java while MeeGo apps in C and other languages like python, but mostly they are written in C and that's what Nokia is pushing indirectly. Even if it is Qt, it's still C. Also Nokia changed the debian packaging to RPM packaging. Is Nokia ready to handle multiple architectures for MeeGo? Android apps are written once and they run everywhere. MeeGo apps will most probably need to be recompiled (at least) once for each architecture, just like Debian packages. I personally find this to be a very very hard obstacle for MeeGo adoption and app development. Consider that each app creator will have to provide packages for multiple architecture, something that only Debian does well. A commercial app that is distributed outside of the official repositories will have to be provided for multiple platforms, meaning that the app creator will have to compile it for multiple platforms. Considering the number of different current and future platforms out there, this is a VERY VERY hard problem to solve (if it is solvable at all). For example, an app vendor starting to develop in 2014, will still have to support hardware that was provided in 2011. From what I can see, this can only be solved if Nokia starts using a language that does not need recompilation everywhere, like Python and Java. Do you have any hints/thoughts on that? |
Re: Meego vs Android apps (C or Java?)
recompiling and fixing a few port issues is really no big deal. For C/C++ developers its part of the development cycle.Non issue for experienced devs
|
Re: Meego vs Android apps (C or Java?)
Quote:
It's not an issue of whether "it is possible" from the developer PoV. It's mostly like this: why write an app that needs adoption for 123745329876 different hardware platforms? And how can this app be supported properly? This breaks the whole "one global app repository" idea, unless something like Debian happens inside Nokia (which I doubt). Android solves this by using Java and Apple solves this by having one platform. This is somewhat similar to the problem of supporting different OS versions. |
Re: Meego vs Android apps (C or Java?)
With C/C++ you have to recompile, with Java you need to have a JVM compatible with the target host, so no big differences imo...
If Dalvik is so portable, why we don't have it on Maemo? |
Re: Meego vs Android apps (C or Java?)
Quote:
As for Dalvik, well.. the libraries seem to be tied to the OS. |
Re: Meego vs Android apps (C or Java?)
Quote:
If you're trying to create a professional app for a particular hardware platform, you're going to want to put some effort into customizing it for the peculiarities of that platform, regardless of the language you prefer to use. |
Re: Meego vs Android apps (C or Java?)
Quote:
|
Re: Meego vs Android apps (C or Java?)
Quote:
|
Re: Meego vs Android apps (C or Java?)
Quote:
Quote:
Quote:
|
Re: Meego vs Android apps (C or Java?)
Quote:
Quote:
Quote:
FWIW, the only available methods for doing this, as far as I know, are:
but you're free to correct me. Also, please don't be offensive. I could also offend you very easily for not replying correctly. |
All times are GMT. The time now is 04:10. |
vBulletin® Version 3.8.8