Hacker News Reader

Comment by uxp8u61q | Hacker News Reader

> That's literally the explanation for PowerShell. Many of us wanted to improve cmd.exe, but couldn't.

I stopped reading here. (Not really, I read the rest, but I could have.)

Powershell is a fundamentally new thing that's miles ahead of its competitors. They couldn't have gotten there by just improving cmd incrementally. If the authors confuses boldness with being carefree about maintenance, that's on them.

View on HN

I'm not a user or fan of powershell, but let me tell you something funny... The creator of Powershell did it as a side project at Microsoft and got DEMOTED for doing it. That's about all you need to know about the culture of Microsoft in the Steve Ballmer years.

That's literally the opposite of what the OP claims, then.

Opposite? It's basically exactly what the OP was alluding to in 2013

OP claimed that pwsh was started because it was new and shiny and would lead to a quicker promotion than working on cmd. Turns out that the guy who created pwsh didn't get promoted, but actually demoted. If you can't understand that demotion is the opposite of promotion, well...

PowerShell was a fundamentally new thing 15 years ago, years pass and I still use zsh and have no desire or motivation to use PowerShell.

It is no longer hyped but also never got a killer app, so it is stuck at "exists" phase.

Until I started working at a SaaS company shipping to Windows enterprise customers I thought PowerShell wasn't used by anyone. Now I see it all the time. It's not fantastic, but if you're in the Windows world it beats writing CMD scripts.

As an end user though I imagine most people use bash or some other unix-world shell, especially post WSL. The "Git Bash" distribution is surprisingly useful as an everyday Windows shell.

You can install any scripting language, you can use Python or Lua for instance. PowerShell has a good integration with the OS, however and you don't need to install other tools if you want to download something or make a web request, for example.

But does it beat curl? The main sellong point of bash is git and curl nowdays. Developer tools can craft curl invocations for web requests. Can they do powershell snippets?

UPD: I've just checked it and yes - Chromium developer tools can produce PowerShell snippets. Good.

Some organization's policies prohibits the installation other interpreters. Not because they're different interpreters; the policy is only the bare absolute minimum for that specific server to accomplish that role gets installed. Reasoning being that the more software you stuff into any server, the more chances that something that isn't supposed to be there has to get into the software supply chain.

So if Powershell (which is inbuilt in Windows) can do everything that python does, even if it's harder and clunkier to work with, guess what you're stuck with.

The only problem with PowerShell (for me) - it came too late. If it was released with .NET 2.0 or 3.0 - maybe I used it more.

When it appeared I already used bash(from git distribution) and python for scripting tasks

tbf in 2013 Powershell was a lot less powerful, and certainly didn't have the institutional support is does today.

Reply on news.ycombinator.com