Suggestion: port Dalvik JIT to Maemo - Page 5 - maemo.org

ivgalvez | # 41 | 2011-01-25, 13:59 | Report

All this useless rants are the same that we heard about Wine years ago...

Dalvik for Linux (not only Maemo) will be extremely useful when there is no better replacement for a particular application.

The only difference with Wine is that Dalvik is OSS and 'should' be easier to port than reverse-engineering the Windows APIs.

The Following 3 Users Say Thank You to ivgalvez For This Useful Post:
Helmuth, Viqsi, zimon

zimon | # 42 | 2011-01-25, 22:34 | Report

Java makes sense in modern C.S. more than C++. Dalvik partly makes more sense than current Java.
Python could conquer, but it needs automatic heuristic static typing JIT VM, and there is none yet.

Qt is in PyQt, QtJambi and why not in QtDalvik.

Meego will fail if it is too dependent on C/C++.

attila77 | # 43 | 2011-01-25, 23:32 | Report

If the available dalvik source really is complete, the real difficulty is integrating it with the rest of the system, i.e. wrap the Maemo APIs into Android ones, which can get tricky, esp when it comes to ones that are undocumented and/or closed. I do think it would be slower overall because system processes/launching are done very differently in Android, plus of course the overhead of the wrappers and the occasional headache of replicating NDI. QtDalvik as such to me makes no sense - you don't get the advantages of either Qt or Dalvik, more like just the drawbacks of both.

The Following User Says Thank You to attila77 For This Useful Post:
Helmuth

jaimex2 | # 44 | 2011-01-26, 15:11 | Report

Originally Posted by attila77 View Post

If the available dalvik source really is complete, the real difficulty is integrating it with the rest of the system, i.e. wrap the Maemo APIs into Android ones, which can get tricky, esp when it comes to ones that are undocumented and/or closed. I do think it would be slower overall because system processes/launching are done very differently in Android, plus of course the overhead of the wrappers and the occasional headache of replicating NDI. QtDalvik as such to me makes no sense - you don't get the advantages of either Qt or Dalvik, more like just the drawbacks of both.

Whats funny is that if the Dalvik port were to happen apps would probably run faster as Android doesn't kill anything and lets them pile up in memory.

dmberta | # 45 | 2011-01-26, 18:20 | Report

Originally Posted by mikecomputing View Post

I dont say people here a not smart something like that. I am just a realist.

Lets give another Example: the open flash that I have forgoten the name of can it compete with Adobe closed one? No it cant and probadly never will. Same goes for an Dalvik clone too N900. And again why should developers here bother try it when those smart developers can do better apps directly in QT/Quick and make it work far better in QT than in Dalvik clone? Dalvik on N900 would be slow and then again people here would start complain and say "hey why is N900 so slow HTC is much faster blablabla..". Seriously it is an impossible mission make it work smooth..

If ýou or another developers can show I am wrong fine for me. But atm. I dont see any good reason to port it.

My tip to all android fanboys who want that X/Y/Z app is to hint the Maemo developers about it (maybe setup a new forum thread like:"Android apps I want to see in Maemo/Meego") maybe some of them have some time to port it to QT/Quick and even make it better than the original Android one :-D Imho its far better use time for this than try to make a dalvik clone. Because I am sure it will never will work.

Btw. about twitter here is an app that maybe is what N900 one example what N900 is lacking atm but will progress faster now when QTQuick is getting more stable :-D

http://thehandheldblog.com/2011/01/1...-qml-download/

I am sure we will see more 2011..

Qt/Quick is here to stay

You assume that all the Apps someone might want to make available could be developed by the Maemo community. For instance, services like Kindle and Audible which provide gateways to paid content on Android and iOS; tell me how you would just make an Audible compatible program? As far as I know its something they have to do, and yes while I have emailed them asking for support, I can't make them do it. So, would it be conceivable that I might want to try to make their Android app run on the N900(yes!)?

attila77 | # 46 | 2011-01-26, 19:04 | Report

Originally Posted by jaimex2 View Post

Whats funny is that if the Dalvik port were to happen apps would probably run faster as Android doesn't kill anything and lets them pile up in memory.

Yeah, you don't have to wait to pile up, given hildon and Qt, it's already full !

But honestly, Android is not too good with that memory management even though it has thrown out all the userspace Linux stuff - having all that Maemo stuff there is not going to help you.

lolloo | # 47 | 2011-01-26, 19:41 | Report

WOW wow wow

dmberta | # 48 | 2011-01-26, 20:16 | Report

http://www.phonearena.com/news/RIM-t...evices_id16245

Playbook might be using Dalvik. Its such a crazy idea that RIM is even considering it.

devu | # 49 | 2011-01-26, 20:47 | Report

Originally Posted by dmberta View Post

http://www.phonearena.com/news/RIM-t...evices_id16245

Playbook might be using Dalvik. Its such a crazy idea that RIM is even considering it.

No is not as crazy as you might thing.

And I have to say I wish Playbook the best on the market. Good native OS and descent API, virtual tools for emulation and development.
Very nice implemented memory management that can handle even multiple (yea Flash) AIR applications, along with native once Java and now this. They will get immediate access to all devs from many platforms and all their experience.

Holy wars between I hate flash or java because I am python or C no longer are relevant. Let's your content to speak for itself and see witch one is going to succeed from end user point of view.

This is my analysis base what I can see around RMI Playbook.
Personally as developer I've never ever considered to buy any BB stuff. But this approach would help me change my mind. And Playbook is on my top list at the moment. I feel tired about those techy wars. what is better or worst. Which OS. Basically there is no the best in all the areas we really wants. As End Users and Developers. because of close parts, companies platform protectionism etc. Once again I see that BB is going to break this wall. Hope so...

You know what?

1. End customer is not giving a s*** about what you thing is better to write a content.
2. Even the best technology in wrong hands can destroy its beauty and you know that even by looking at some "very well ported or written" stuff for N900. Written the best and efficient way possible right?

Last edited by devu; 2011-01-26 at 20:50.

The Following 2 Users Say Thank You to devu For This Useful Post:
dmberta, mesz

ymartin59 | # 50 | 2011-01-27, 17:12 | Report

Even Nokia considers that option - I get an email from project leader - for MeeGo, either the way I'm investigating: compiling dalvik sources against Maemo/Linux API or with a cross-compiler probably from application binaries to Qt.

Last edited by ymartin59; 2011-01-29 at 07:40.

The Following User Says Thank You to ymartin59 For This Useful Post:
maluka