iseahound wrote: ↑
24 Jul 2020, 12:36
Re: AutoHotkey v2 becoming a general purpose programming language, I think that is a good thing. The language is getting stronger and for a good reason. That reason is so that modern libraries such as Tensorflow and OpenCV can one day be integrated into AutoHotkey. If you think about it, despite Python being great at processing data, it is not so good at windows automation without importing a few libraries.
Lastly, the biggest factor for me is AutoHotkey not staying in touch with future forms of interaction such as speech/voice input, camera input, etc. I suppose these could be user created libraries, but lacking multi-touch (when everything is touch screen!) isn't an excuse.
I do agree that AutoHotkey's small executable and portability is it's greatest strength.
I just hope its not flirting with disaster in terms of community split, somewhat like Python 2 VS Python 3 did to its community. Removing of what appears to be "unneeded" noob friendly features to satisfy advanced tastes, could possibly cause people to want to stay with AHK v1 or a new AHK v1 fork, while many of the so-called advanced AHK v2 users might get seduced to other programming languages. "Well, now that I'm doing general purpose programming with AHK, let me just jump over to..." I can't speak for arcticir, but that's the kind of vibe his original post gave off.
But automation is a very wide field. There are so many things to factor in; speech, voice, touch screen, RPA, RDA, AI, digital assistant, etc... There debatably is no reason not to stay close to this lane, and keep knocking it out. And this mindset or focus, is likely to be reflected in the AHK language development (automation centric VS general purpose).
For example, I started using AHK, because it wasn't
If AHK becomes more like other general purpose programming languages or
I can't say what "thee answer" is, outside of a feeling or hunch, but it does appear a bit worrisome.