Live data from Hacker News

Android: The Land That Python Forgot

speakerdeck.com

21–30 of 127 posts

Re: Android: The Land That Python Forgot

#21
post #6
post #5

What'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.

Couldn't a language-bridge library use Java reflection to accomplish a lot of what's needed?

Re: Android: The Land That Python Forgot

#22
I'd point out that Python was the preferred high-level language at pre-MS Nokia. There was Python for S60 for a long time, even before either iOS or Android existed. More recently Nokia made new Python bindings for Qt, PySide, to be used on Maemo.

Re: Android: The Land That Python Forgot

#23
post #11

You 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…

If you think Python is a worse Java then there is something important you have missed.

If you think that programming languages are strictly worse or better than others on a linear scale, then there is something important you have missed.

Re: Android: The Land That Python Forgot

#24
post #10

Just 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?

looks awesome but i've never been able to install it on my windows machine ,it complains about my graphic card. But it looks neat.

Re: Android: The Land That Python Forgot

#25

You 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…

"write a Python compiler for iOS or Android to make it compelling, which means adding type checking " No PyPy is a (JIT) compiler for Python, no type checking addition needed.

the point is adding type system, not compiling it.

Re: Android: The Land That Python Forgot

#28

You 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…

Lua can easily be compiled and used on both Android and iOS.

Re: Android: The Land That Python Forgot

#29

You 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…

I like to add some more.

That's correct that the type system is the crucial attribute as a platform language. But that's not the only reason. It's also for correctness, safety, productivity and manageability.

That's because a platform is huge and complex monster. So all those properties are archive-able only by automated tools, and those tools need rich metadata for each word of code. Type information is crucial metadata, and it's mostly impossible to make high quality tools without those informations. That's why all the designed modern platform (=system) languages are all mostly typed. From C/C++/Objective-C, to Java, C#, Go, Rust, Dart, TypeScript…

In fact, it doesn't matter the language actually statically typed, dynamically typed, duck-typed, or completely untyped. The point is an ability to offer accurate metadata for automated tools, and type system is the best ever invented. So languages lacks the ability cannot be a platform's primary language.

Post reply on HN