this reminds me of yossi kreinin's 'i can't believe i'm praising tcl' <a href="https://yosefk.com/blog/i-cant-believe-im-praising-tcl.html" rel="nofollow">https://yosefk.com/blog/i-cant-believe-im-praising-tcl.html</a><p>tcl, like bash, makes some of the same decisions as autohotkey: literal strings are unmarked, while variables to use the value of are marked, and you can invoke commands without parentheses around their arguments<p>yosef makes a good case that these are the right choices for a command language only occasionally used for scripting, like tcl, but i wonder if they were also the right choices for ahk, however much they may have screwed up the details<p>like, requiring commas between arguments is probably bad? especially between the command name and its arguments? pv-wave idl is the only thing i've ever used that made that mistake<p>from the degree of annoyance my wife is having with the & required by scanf in c (she knows more lua than c but the class she's taking is in c), i predict that ahk 2 will not be very popular with ahk 1's audience, who mostly don't know any other programming languages<p>i'm interested to know what the best alternatives to ahk are for x11 and wayland, even if they do require being a programmer (i am)