Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
Aren't we glad it's 2016 ?
Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
221–230 of 350 posts
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#222Windows fan here. I hate PowerShell and I'd much rather have Bash built into Windows. Things I hate about PowerShell: - You can't even run your own scripts without performing the Set-ExecutionPolicy ceremony first or signing your scripts. - It's way too verbose. - It's a strange bird that next to nobody uses, so there's zero motivation to learn it. - It's not "old reliable". You can't depend on it working due to the…
Literally every windows admin uses it. It's the official commandline interface for microsoft software. Every piece of microsoft software must provide a ps interface. It's an engineering directive.
"admin"
This would be a good move if it was on Windows Server.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#223That's nice. Can you pipe binary data without powershell corrupting it, or is that now a feature? https://brianreiter.org/2010/01/29/powershells-object-pipeli...
It's amazing, isn't it. They went to the effort of building a typed shell but didn't realise there are multiple different types of string. I bet it still truncates output of the ">" operator to the console width, too.
[deleted]
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#224Windows fan here. I hate PowerShell and I'd much rather have Bash built into Windows. Things I hate about PowerShell: - You can't even run your own scripts without performing the Set-ExecutionPolicy ceremony first or signing your scripts. - It's way too verbose. - It's a strange bird that next to nobody uses, so there's zero motivation to learn it. - It's not "old reliable". You can't depend on it working due to the…
Literally every windows admin uses it. It's the official commandline interface for microsoft software. Every piece of microsoft software must provide a ps interface. It's an engineering directive.
It is strange to claim no one really uses powershell. It is widely used in the Windows world.
The main complaint I see about powershell is that it isn't bash. The object pipeline in powershell can be so much more powerful than parsing text between commands. After all, that's why we have data types instead of storing everything in strings.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#225Powershell is very insecure and is heavily abused by potential attackers as it's more flexible than CMD.exe. Of course, arguing about CMD.exe vs PS.exe is pointless, but it still needs to be argued. There has been a recent spate of talks in Blackhat conf. and other confs, about the versatility of PS.exe, how it is used to perform persistence in comparably little characters, or lines of script than CMD.exe Some of my…
Strange. Because its bloody hard to get powershell to run anything with default security settings.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#226That's nice. Can you pipe binary data without powershell corrupting it, or is that now a feature? https://brianreiter.org/2010/01/29/powershells-object-pipeli...
It's amazing, isn't it. They went to the effort of building a typed shell but didn't realise there are multiple different types of string. I bet it still truncates output of the ">" operator to the console width, too.
'troll' * 1000 > out.txt
Were you using |format-table and |format-list (ft, fl) to explicitly format the text for console viewing, then redirecting that to a file?
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#227Earlier quoted context omitted.
Literally every windows admin uses it. It's the official commandline interface for microsoft software. Every piece of microsoft software must provide a ps interface. It's an engineering directive.
It is strange to claim no one really uses powershell. It is widely used in the Windows world. The main complaint I see about powershell is that it isn't bash. The object pipeline in powershell can be so much more powerful than parsing text between commands. After all, that's why we have data types instead of storing everything in strings.
It's not widely used in the Windows world from what I can see.
Walk into any office and ask an IT guy to run "ipconfig". They'll open up cmd.exe without even thinking about it.
I read a lot of programming tutorials. Nobody ever reference PowerShell in them. They always instruct people to open cmd.
Do you have any evidence to the contrary?
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#228Why ? Because some linux zealots think it's the best option ? Laughable.
Hey, I'm still on Windows desktop after having tried Linux desktop more times than I can count. But to claim that bash (or most other shells) are only preferable to cmd and powershell if you're a linux zealot is what is truly laughable. If you have ever worked with both there would be no question.
[deleted]
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#229Earlier quoted context omitted.
It is strange to claim no one really uses powershell. It is widely used in the Windows world. The main complaint I see about powershell is that it isn't bash. The object pipeline in powershell can be so much more powerful than parsing text between commands. After all, that's why we have data types instead of storing everything in strings.
It's not widely used in the Windows world from what I can see. Walk into any office and ask an IT guy to run "ipconfig". They'll open up cmd.exe without even thinking about it. I read a lot of programming tutorials. Nobody ever reference PowerShell in them. They always instruct people to open cmd. Do you have any evidence to the contrary?
For simple tasks such as running a command, sure. But if that admin needs to do anything more complex, such as parsing the output of ipconfig, they're most likely going to use powershell.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#230Earlier quoted context omitted.
I don't know for sure about ZSH and can't test it at the moment, but Bash has -- for this purpose. It may work in ZSH as well.
Isn't the -- a feature of the command to stop option parsing and treat the remaining arguments as file names? AFAIK it's not a shell feature that solves quoting (and it's not that easy on Unix either, since running a program involves argument parsing instead of just passing a string).
You could define `--` as "perform no expansions for the rest of the line", then you wouldn't have to worry about globs or `{}` which is where most of my annoyances come from.
BTW `--` isn't treated specially in version 4 of Bash.