Re:Android P
by tomp on Tuesday May 08, 2018 @07:17PM
(#17026205)
Building an app is way too much barrier to entry... What I wish is something like, right-click or swipe down to open console, enter some script (or copy-paste/import a highly starred from a public repository), close console, ta-da. If the API was flexible enough, the scripts would mostly be short and obviously non-exploiting (i.e. a script for graying-out the screen shouldn't use the internet API) so they would be very easy to review, modify, and manage otherwise.
[ Parent
| on HN ]
A few steps further you will invent something like Emacs. Or maybe Atom. Or browser extensions.
BTW do you remember why making a browser extension is a bit involved, and publishing, even more so? Trusting someone else's code. Copy -pasting it from a message board may end up in a problem.
That sounds more like a sandboxing/permissions problem... Also, it doesn't help that JavaScript is a terrible language.
Re:Android P
by hahainternet on Tuesday May 08, 2018 @07:48PM
(#17026358)
https://github.com/damonkohler/sl4a has been around in one form or another for a decade or so.
It looks dead in that repository though.
Re:Android P
by icebraining on Wednesday May 09, 2018 @06:38AM
(#17028794)
http://www.qpython.org/ seems pretty well.
Hmm for this specific case I think that there might be a lot of of edge cases, just a gut feeling
But I would totally be for some much simpler packaging scheme for native apps/"scripts". It's kinda insane how much money is going into Android from Google but all the dev tools are basically just Java stuff. I really wonder what Android could be if a more lisp-y approach existed as well