Windows PowerShell Tutorial
dispatchertimer.com
Windows PowerShell Tutorial
1–9 of 9 posts
Re: Windows PowerShell Tutorial
#2PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
Re: Windows PowerShell Tutorial
#3PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
So basically it would be awesome if it wasn't powershell?
On that basis I agree, because the encounters I've had with PS have been nothing but horrid.
It's slow, obtuse, complicated and unpredictable. cmd+rundll32 was far nicer and that's saying something
Re: Windows PowerShell Tutorial
#4PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
PowerShell is awesome. A shell with proper intellisense, a real object pipeline, string interpolation and cool meta-programming facilities - to mention just a few areas where it runs rings around bash.
Re: Windows PowerShell Tutorial
#5PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
So basically it would be awesome if it wasn't powershell? On that basis I agree, because the encounters I've had with PS have been nothing but horrid. It's slow, obtuse, complicated and unpredictable. cmd+rundll32 was far nicer and that's saying something
It's much, much better than cmd.exe. Not even in the same league.
Plus, you can pipe objects around, which is better than piping strings, because strings are objects too. So it's a "superset of string-piping", though obviously, not a superset of bash. The syntax is weird and lots of non-intuitive stuff about PowerShell, but it's definitely at least 1,000x better than the default windows console.
Re: Windows PowerShell Tutorial
#6Earlier quoted context omitted.
So basically it would be awesome if it wasn't powershell? On that basis I agree, because the encounters I've had with PS have been nothing but horrid. It's slow, obtuse, complicated and unpredictable. cmd+rundll32 was far nicer and that's saying something
It's much, much better than cmd.exe. Not even in the same league. Plus, you can pipe objects around, which is better than piping strings, because strings are objects too. So it's a "superset of string-piping", though obviously, not a superset of bash. The syntax is weird and lots of non-intuitive stuff about PowerShell, but it's definitely at least 1,000x better than the default windows console.
The syntax is weird and lots of non-intuitive stuff about PowerShell
That's simply enough to kill it for me.
That and patchy culture support crudely derived from the CLR where the script will parse/emit dates as 11/12/13 on one host and 12/11/13 on another host based on some random combination of system locale (sometimes even when they're the same!!!) and solar cycles. They managed to make it non portable on the same platform!
Piping objects is a pain as well. You suddenly have a type contract on a pipe which makes things incredibly brittle if you have to refactor anything. Dealing with strings be they delimited or not is considerably easier.
Re: Windows PowerShell Tutorial
#7PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
It would have been (more) awesome for me if it ran on Linux too.
There is an effort to get it running with Mono - https://github.com/Pash-Project/Pash
Re: Windows PowerShell Tutorial
#8PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
PowerShell is awesome. A shell with proper intellisense, a real object pipeline, string interpolation and cool meta-programming facilities - to mention just a few areas where it runs rings around bash.
There is even PSReadline - https://github.com/lzybkr/PSReadLine
Re: Windows PowerShell Tutorial
#9PowerShell would have been awesome if it were a proper superset of bash and they released the code under a GPL, Apache or BSD kind of license.
PowerShell is awesome. A shell with proper intellisense, a real object pipeline, string interpolation and cool meta-programming facilities - to mention just a few areas where it runs rings around bash.
And that buys you absolutely fuck all.