As a software centric engineer finishing up my second decade of professional work I knew python from the early 2.x versions. Watching and usiyit for automation mostly on winOS (starting from good old Windows 2000). As my personal Hardware moved more and more to the Apple ecosystem I was always eager to get automation on iOS/iPadOS. This summer vacation I set myself the challenge to dive deeper to automation with Java Script on iOS - after quite some years of playing around with Pythonista. Most pro apps like Drafts do have a quite impressive JS framework for automation sometimes with great libraries (TADpole) and Examples and an open and helpful community (here or over at forums.getdrafts.com).
After the first quarter of JS on iOS my aversion to JS as a first language to learn is still controversial.
Firstly because many of the core is in fact based on C as a programming language- good for all who know that .
Secondly because most of the tutorials are heavily targeted for HTML usage or add the great and convenient nodeJS runtime - both do confuse users who just want to learn automation.
Thirdly because the higher abstractions in coding (classes, protocols, user interfaces) are not obvious in JS.
This is why I still would recommend Python (Py) as a better choice for first language experience.
This results in a threefold call to action:
One: To the users to look at the language and reply their insights and evaluation (JS vs PY) to the others.
Two: To the python developers to acknowledge iOS, Android and iPadOS as a target plattform and start releasing on it (Pyto is an iOS App with all sources on github, beewares Tofu is a python project that has this in mind but is pretty far from completeness
Third: To the app developers to reconsider the only JS approach in their apps. There could be a not so obvious back door via Python transpiration to JS if the full Python engine or the micro Python engine is too much effort.
What do you think?