3 ms·
I am amazed that there is such misunderstanding of PowerShell. I partially blame Microsoft because of their idea to aggressively recommend non-aliased PowerShe
by majkinetor 5y ago
I am amazed that there is such misunderstanding of PowerShell.
I partially blame Microsoft because of their idea to aggressively recommend non-aliased PowerShell for EVERYTHING (it backfires entire decade and they still do it, along with the army of "MVP"s, which is amazing head in the sand behavior when entire Internet bitch about it) and because they obviously don't manage user education well.
I then blame everybody else for not RTFM and always complaining about the same nonsense: verbosity, performance, missing short circuit bashizm etc.
Seriously people - PowerShell is one of the best inventions since the first computer that you can use on any OS. If you didn't grok it, its about ====> YOU <==== not about PowerShell.
Once the only real issue is solved (performance is not greatest, but not too bad either), it would border to incompetence to not put it by default on any OS.
- rasz 5y agoDoes PowerShell offer anything I couldnt do with https://www.autohotkey.com https://www.autohotkey.com in a much friendlier manner?
- majkinetor 5y agoYes. Speaking as someone who has a lot of experience with both (see my github) - Cross platform - Extensive Integrations and 3rd party ecosystem - Generally much shorter code for the same stuff - Package manager AHK was never considered a general purpose language nor a good language. I was probably one of the first people to use it that way (See Forms framework). With AHK2 incoming it is much better language (although Lua would be way better instead). AHK is oriented toward GUI automation, PowerShell toward CLI automation. AHK is not there out of the box on any Windows. You can basically do anything in anything, but that doesn't mean you should. https://github.com/majkinetor/mm-autohotkey https://github.com/majkinetor/mm-autohotkey