4 ms·
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 o
by Throwadev 13y ago
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.
- csmuk 13y agoThe 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.