Aha! A folder full of .ps1’s (that were .ahk’s) begs to differ on this point :-)
Some random examples i use all the time:
* i have a bunch of apps (i think of it like a workspace) that i open for specific tasks - e.g. when playing ham radio i’ll open a tool that lets me duplicate traffic to/from a serial port (com0com) so that multiple apps can share 1 physical port, a tool that lets me control my radio (flrig), a tool that lets me route audio between devices and software without a mess of cables doing it in hardware (voicemeeter banana), a tool that encodes/decodes messages (wsjtx), a tool that shows what grid squares i’m hearing (gridtracker) and a tool for logging (home brew). They all need to be arranged in fairly bespoke ways across a couple of screens to let me work effectively - bind the shortcut to the .ps1 to a keyboard shortcut and i’m done.
The same idea exists for my other workspaces (dev work - there’s different flavours for this one by task, photo editing, researching, presenting, etc. Etc.)
Things like sending “PS1;” CAT control command to my radio (this turns it on) are actually less lines of code in .ps1 than .ahk. My .ps1’s are about 2/3 the size of the .ahk’s in practice.
Before .ahk i was using python2 with the win32 module, .ps1 is comparably expressive to python2 - which surprises me.
Other .ahk’s i use all the time are basically glorifed macros for common actions i perform. Again shorter to express in powershell.
> A folder full of .ps1’s (that were .ahk’s) begs to differ on this point
I have tones of ps1 and tones of ahk files in folders. But its not comparable. Main use case of AHK is GUI automation, which is precisely not something powershell handles nor it will ever be in its scope.
Some random examples i use all the time:
* i have a bunch of apps (i think of it like a workspace) that i open for specific tasks - e.g. when playing ham radio i’ll open a tool that lets me duplicate traffic to/from a serial port (com0com) so that multiple apps can share 1 physical port, a tool that lets me control my radio (flrig), a tool that lets me route audio between devices and software without a mess of cables doing it in hardware (voicemeeter banana), a tool that encodes/decodes messages (wsjtx), a tool that shows what grid squares i’m hearing (gridtracker) and a tool for logging (home brew). They all need to be arranged in fairly bespoke ways across a couple of screens to let me work effectively - bind the shortcut to the .ps1 to a keyboard shortcut and i’m done.
The same idea exists for my other workspaces (dev work - there’s different flavours for this one by task, photo editing, researching, presenting, etc. Etc.)
Things like sending “PS1;” CAT control command to my radio (this turns it on) are actually less lines of code in .ps1 than .ahk. My .ps1’s are about 2/3 the size of the .ahk’s in practice.
Before .ahk i was using python2 with the win32 module, .ps1 is comparably expressive to python2 - which surprises me.
Other .ahk’s i use all the time are basically glorifed macros for common actions i perform. Again shorter to express in powershell.