The reality is that the tools (cython, python) were built without mobile platforms in mind, and they (currently) are ill suited to supporting them. That's not the platforms fault; it just an artifact of the development history of the projects.
Cython is not a general purpose compile to C solution. It solves a different problem to Rusthon.
/shrug
Except, Python does work on them.. no one's blaming the platform. Everyone is at the same disadvantage on non-native platforms as everyone else. No ones blaming it. It's just that it's a hard think to retrofit -anything- to Apple or Google's platform that isn't ObjC/Java.
Python is further along here than most, which should be commended.
It is in question. I hate people with these narrow-minded viewpoints as if there's not a ton of flexibility and creativity going on with programming. It's preposterous and you must have a grudge or ulterior motive.
Python is not a stationary target with a fixed set of pros/cons. It's changing all the time.
In fact, I do what you're suggesting it isn't good for, all the time. Distributing single-binary applications using PyInstaller and Nuitka.
Shared library per module and 'wrapped' compiler execution for example, is fundamentally hostile to distribution for mobile environments. Have a look at the hoops kivy-ios jumps though. It's absolutely ridiculous.
That's the thing python is the worst at; building a single stand alone application that does not require the user to install a copy of python and run pip to download a million dependencies before it will run.
This isn't in question. It's just life; that's not what python is good at.
Cython doesn't solve that problem. It solves a different set of problems; namely, ffi and speed.
My point is that by choosing an alternative approach (compile to portable C++ / rust) this project gives you the benefits of ffi and speed and distribution.