Hacker News Reader

Comment by Alupis | Hacker News Reader

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 commands is super "Microsofty" if you know what I mean.

I get around by using Git Bash (which is actually quite good for being a bundled afterthought), cygwin, or lately even WSL containers.

View on HN

Git Bash, cygwin, WSL containers are all completely different things. PowerShell is a shell like bash, just with a different syntax.

What different things do you think it is trying to be?

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-Functio...

[1] - https://fuzzysecurity.com/tutorials/24.html

Reply on news.ycombinator.com