Just a quick thought about the future of Termux.
Termux or its successor will have to register itself as an app manager (like F-Droid), and it probably needs to ship its own version of `install` which locally builds and signs an APK as an addon for the Termux app.
So Android has been moving for years towards making it impossible for something like Termux to exist -- making it so that apps cannot download/create new executable code.
Basically W^X at the file system level, except that you can't explicitly disable it when it would be useful.
Towards that end, they've been slowly choking out Termux's ability to even install/run. It has to be built against an old Android API version, which for years hasn't been allowed on the app store, and nowadays trying to sideload the APK requires you to go through extra warnings/hurdles.
So I think Termux or its successor
Except that CPUs and serious operating systems provide W^X as a default, while letting programs disable that default for pages of memory. This enables JIT compilation.
I'm not entirely sure how this is supposed to add security in itself, unless they intend to eventually tighten the noose further and disallow code interpreters as well. Most charitable version is that they still let you have things like Python in your app, but require the app to declare a special scary permission -- but if they do that, they should









