My guess is that it's still Java-like under the hood -- at the very least, calling out to API endpoints will be... Probably doesn't change much at all. (Though I'd love to be wrong).
Not really -- most mobile code is simply glue for UI event handlers and the like. And Python's really good at writing glue code. Just like when you're coding in Java, code that needs performance is native, and written…
Yup. If we had Jython, this talk wouldn't have needed to have been written. And I'd probably be working to improve Jython as we speak.
You're running the Python interpreter as a native executable, so it's roughly comparable to Dalvik. If you want performance, write it in C, optimise it. That's what the NDK is for.
The talk was at mostly web developers. The second and third parts of the talk were about why the web doesn't cut it as a platform. Part 1 was there to lay the groundwork. Basic? Maybe, but it's necessary.
It's a possibility – Qt's there, and in fact Kivy is a pretty good solution. The problem I raise in the talk is that such libraries will always lag behind the state of the art for Android GUIs, which makes them less…
That's pretty much exactly what python-on-android does; the problem is that you don't get access to any of the Java/Dalvik-based libraries, which includes all of the UI programming libraries.
Ohai! I wrote the talk, and just want to let you know that you can watch it over at https://www.youtube.com/watch?v=p77BR6e1uoo --Chris
My guess is that it's still Java-like under the hood -- at the very least, calling out to API endpoints will be... Probably doesn't change much at all. (Though I'd love to be wrong).
Not really -- most mobile code is simply glue for UI event handlers and the like. And Python's really good at writing glue code. Just like when you're coding in Java, code that needs performance is native, and written…
Yup. If we had Jython, this talk wouldn't have needed to have been written. And I'd probably be working to improve Jython as we speak.
You're running the Python interpreter as a native executable, so it's roughly comparable to Dalvik. If you want performance, write it in C, optimise it. That's what the NDK is for.
The talk was at mostly web developers. The second and third parts of the talk were about why the web doesn't cut it as a platform. Part 1 was there to lay the groundwork. Basic? Maybe, but it's necessary.
It's a possibility – Qt's there, and in fact Kivy is a pretty good solution. The problem I raise in the talk is that such libraries will always lag behind the state of the art for Android GUIs, which makes them less…
That's pretty much exactly what python-on-android does; the problem is that you don't get access to any of the Java/Dalvik-based libraries, which includes all of the UI programming libraries.
Ohai! I wrote the talk, and just want to let you know that you can watch it over at https://www.youtube.com/watch?v=p77BR6e1uoo --Chris