2 ms·

I personally have found PowerShell to be obnoxious. It doesn't seem to know what it's supposed to be and tries to be everything all at once. The syntax for comm

• sbelskie 3y ago
  What different things do you think it is trying to be?
  • therein 3y ago
    I have nothing against PowerShell. I've used it for avoiding detection etc. in the past. Fun tool that surprises and delights in unexpected ways. It is pretty powerful/insane that stuff like this is a part of PowerShell and that's probably what the GP is talking about: Add-Type -TypeDefinition @" using System; namespace DemoCode { public class DemoClass { public static void WriteHello() { Console.WriteLine("Hello"); } } } "@ [DemoCode.DemoClass]::WriteHello() Or LoadLibrary call and invocation from PowerShell. [0] [1] It blurs the lines as to what it is no matter how you look at it. In contrast, try doing that in cmd.exe or invoking a function from a shared object after getting a pointer to it using dlopen through a POSIX shell. [0] - https://www.powershellgallery.com/packages/PSReflect-Functions/1.1/Content/kernel32%5CLoadLibrary.ps1 https://www.powershellgallery.com/packages/PSReflect-Functio... [1] - https://fuzzysecurity.com/tutorials/24.html https://fuzzysecurity.com/tutorials/24.html
• TiredOfLife 3y ago
  Git Bash, cygwin, WSL containers are all completely different things. PowerShell is a shell like bash, just with a different syntax.