Live data from Hacker News

Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

news.softpedia.com

281–290 of 350 posts

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#281

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…

What drove me away from Terminal.app was the fact that I can't use command-1/2/3 to switch tabs. Ctrl-tab doesn't work either. Did I miss something?

CMD + { and CMD + }

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#282

Earlier quoted context omitted.

What drove me away from Terminal.app was the fact that I can't use command-1/2/3 to switch tabs. Ctrl-tab doesn't work either. Did I miss something?

CMD + { and CMD + }

I wonder why they chose ⌘{ and ⌘} instead of ⌘[ and ⌘]. With the later you don't need to hold down SHIFT (at least on US keyboard layout.)

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#283
post #144
post #134

Earlier quoted context omitted.

Most Windows terminal people use ConEmu rather than the inbuilt terminal apps - it's like iTerm2 vs Terminal.app on MacOS. ConEmu adds Unix style cut and paste, tabs, etc. Add openssh, PSReadLine and PSCX and you've got a proper terminal setup. Also MS should really improve the inbuilt apps to do this stuff.

Whilst I am glad to hear about ConEmu; I have to disagree, I use windows cmd.exe very regularly, and know lots of other people that do, and I have never used ConEmu before! I might give it a try now I know about it.

ConEmu si really nice simply because you can have tabs, split pane and good color schemes. 've never gotten to the level that some people need, so ConEmu + bash = everything I was using on OSX.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#284
post #3

"Typing cmd in the run dialog will launch PowerShell as well" What? I'm a big PowerShell fan, but I see the need to keep cmd around for a while. Clobbering it before it's phased out seems problematic.

The news article is incorrect. Typing cmd from the run dialog still launches cmd.exe.

The release post spells out exactly what's changes - win-x menu, context menu kind of stuff.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#285

Earlier quoted context omitted.

Compare it with cmd.exe's dir

I have had a quick look through here [1] and most of the answers involve timing precision of two significant digits. By that metric, PowerShell's 2.4ms clocks in at 0.00 seconds. Which means cmd.exe (at a precision of two significant digits) can't beat it. [1] http://stackoverflow.com/questions/673523/how-to-measure-exe...

"2.4" or "0.0024" or "24000" all have two significant digits. Leading and trailing zeros don't count as significant digits.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#286
post #137

Earlier quoted context omitted.

Did you have a choice to upgrade? Could you reinstall the old version of you wanted? Windows has stripped that power from users.

What power was stripped? Cmd.exe is still there.

But making it the default was their decision, and users had no say in the matter since they can't opt out of the update.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#287
post #53

By the way, where does the capitalized kebab case come from? Prior art or just Microsofts general hankering for capitalization (e.g. C#s Class.DoSomething() vs Java's Class.doSomething())?

Note that it's not quite "kebab case". The dash only separates the initial verb from the object, but the rest of it is regular PascalCase. So Get-ChildItem, not Get-Child-Item.

PascalCase is well-established in the Microsoft developer ecosystem. It goes at least all the way back to Win16 and Windows 1.0 (it using the Pascal calling convention might have something to do with it, perhaps).

More importantly, it is used uniformly in .NET, and PowerShell builds on top of .NET, and deals with .NET objects directly, which have properties like e.g. `FullName`. So it makes sense for consistency.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#288

Just another reason to stay away from Windows as a platform. Windows 10 is a moving target if you are trying to work with it.

You say that; and yet [32-bit] Windows 10 can still run 16-bit GUI applications originally compiled for Windows 1.0 back in 1985, more than 30 years ago. We aren't even talking about a recompile here, but straight up binary compatibility.

How many other OS/DE combos do you know that can boast anything similar?

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#289

Earlier quoted context omitted.

What drove me away from Terminal.app was the fact that I can't use command-1/2/3 to switch tabs. Ctrl-tab doesn't work either. Did I miss something?

CMD + { and CMD + }

Thanks but... yuck. Any way I can remap these?

Cmd- is a pretty standard way to jump to tabs (and arguably, Ctrl-tab as well).

Post reply on HN