Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

Post by UnoriginalGuy » Sat, Nov 19, 2016, 1:52 AM UTC

mattmanser wrote: post #310

UnoriginalGuy wrote: post #264

Earlier quoted context omitted.

I'm going to address each bullet: - Set-ExecutionPolicy can be set with a single click from the "For Developer Settings." Just scroll down and hit Apply three times and your machine has sane developer defaults (inc. ExecutionPolicy). - The verbosity means that you can "guess" PS commands. Each PS command is a set layout with an action word (e.g. Add, Clear, Get, Write, etc) and then target (e.g. Set-Alias, Set-Date,…

Guess? With naming conventions like "Get-ChildItem"? Major functionality, probably the worst name you could come up with.

Post by JeffreySnover » Sat, Nov 19, 2016, 2:03 AM UTC

bitwize wrote: post #207

nneonneo wrote: post #166

Earlier quoted context omitted.

I've used iTerm and Terminal on Mac, and the default Windows Terminal (conhost), PuTTY sand MinTTY on Windows. Terminal.app is much, much better than conhost, even after the Windows 10 update. It's fast, supports a ton of thoughtful features (such as customizable title bars via extended ANSI codes, real line wrapping during resize, good Unicode support from the very beginning, etc.). With Terminal.app I can be quite…

> PowerShell's terminal experience is better but not quite there. And, PS suffers from extremely long load times - I've seen it take upwards of 10 seconds to start without any extensions. Small price to pay to be able to pipe objects , man!

Post by JeffreySnover » Sat, Nov 19, 2016, 2:09 AM UTC

brazzledazzle wrote: post #196

gfody wrote: post #176

Earlier quoted context omitted.

Related, running something like decrypt hugefile.dat | encode outfile.dat will usually result in powershell using up all your system ram and crashing.

On a somewhat related note, one of PowerShell's biggest weaknesses is memory utilization. And since they make it so simple to pass around hefty object collections it tends to bite you in the ass early on. Particularly when you're using cmdlets. When doing real scripting that actually needs to be run as a job I am surprised when I can get away with cmdlets and don't need to manage .net APIs/objects directly. Especiall…

Post by JeffreySnover » Sat, Nov 19, 2016, 2:21 AM UTC

6u54wuwu5w wrote: post #2

So, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?

Post by voltagex_ » Sat, Nov 19, 2016, 2:26 AM UTC

ygra wrote: post #88

sveiss wrote: post #52

Earlier quoted context omitted.

You can, but sometimes the quoting rules differ. For example, bcdedit with its {}-delimited GUIDs breaks in PowerShell without additional quoting, but works fine in cmd.exe. Makes following online instructions tricky if you're not familiar with that nuance.

Well, the nice thing in PowerShell is that you have explicit control over "stop parsing here and just pass the rest to the application verbatim" with --%. Solves a lot of quoting nightmares.