Android: The Land That Python Forgot
speakerdeck.com
Android: The Land That Python Forgot
1–10 of 127 posts
Re: Android: The Land That Python Forgot
#2The first half of the deck is about what a smartphone is. You should cut those out and get to the subject matter.
Re: Android: The Land That Python Forgot
#3You can replace Python in Ruby or Lua for the most part and also Android with iOS. Dynamic languages aren't yet a big deal and I think it's because they don't bind well or give you a significantly better developer experience than Objective-C or Java on these platforms do.
RubyMotion is probably the closest I've seen to making a language like Ruby or Python a very compelling mobile developer experience while maintaining the end user experience.
That basically means you need to write a Python compiler for iOS or Android to make it compelling, which means adding type checking and at some point developers start asking why they aren't just using Java in the first place...
Re: Android: The Land That Python Forgot
#4Ohai!
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
Re: Android: The Land That Python Forgot
#5What's wrong with embedding python interpreter as a C library?
Re: Android: The Land That Python Forgot
#6What's wrong with embedding python interpreter as a C library?
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.
Re: Android: The Land That Python Forgot
#7You can replace Python in Ruby or Lua for the most part and also Android with iOS. Dynamic languages aren't yet a big deal and I think it's because they don't bind well or give you a significantly better developer experience than Objective-C or Java on these platforms do. RubyMotion is probably the closest I've seen to making a language like Ruby or Python a very compelling mobile developer experience while maintaini…
the irony is the use of javascript in solutions like Titanium,to code ANYTHING but the ui ( the business logic is in javacript , the ui is native ). I like the approach though, it's a better approach than phonegaps and likes. the only drawback : doesnt seem the engine they use is opensource.
Re: Android: The Land That Python Forgot
#8You can replace Python in Ruby or Lua for the most part and also Android with iOS. Dynamic languages aren't yet a big deal and I think it's because they don't bind well or give you a significantly better developer experience than Objective-C or Java on these platforms do. RubyMotion is probably the closest I've seen to making a language like Ruby or Python a very compelling mobile developer experience while maintaini…
Those languages does not focus on portability.
Re: Android: The Land That Python Forgot
#9What's wrong with embedding python interpreter as a C library?
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.
Do you mean you want something like Mono's Xamarin in Python?
Re: Android: The Land That Python Forgot
#10Just point out, this talk mentions: kivy -- A python kit for a portable, touch-focused UI that works on Android as well.
I used to follow it initially but noticed the project seems to have slowed down. There haven't been as many releases lately. Anyone have more info on why that might be?