为什么不两者都用呢?在Cygwin中调用PowerShell脚本，就像其他解释性脚本(如Perl)一样。

为此，我编写了https://bitbucket.org/jbianchi/powershell，以便Bash包装器在Cygwin中调用powershell.exe。它可以用作PowerShell .exe .ps1脚本的第一行shebang(因为PowerShell也使用“#”作为注释)。参见https://bitbucket.org/jbianchi/powershell/wiki/Home获取示例

PowerShell中的cmdlet非常好，工作可靠。因为我是一名Java/ c#开发人员，所以它们的面向对象性非常吸引我，但这并不是一个完整的集合。由于它是面向对象的，因此它错过了POSIX工具集(例如awk和sed)的许多文本流成熟度。

The best answer I've found to the dilemma of loving OO techniques and loving the maturity in the POSIX tools is to use both! One great aspect of PowerShell is that it does an excellent job piping objects to standard streams. PowerShell by default uses an object pipeline to transport its objects around. These aren't the standard streams (standard out, standard error, and standard in). When PowerShell needs to pass output to a standard process that doesn't have an object pipeline, it first converts the objects to a text stream. Since it does this so well, PowerShell makes an excellent place to host POSIX tools!

最好的POSIX工具集是GnuWin32。它确实需要超过5秒钟的时间来安装，但这是值得的，据我所知，它不会修改你的系统(注册表，c:\windows\*文件夹等)，除了将文件复制到你指定的目录。这是非常好的，因为如果您将工具放在共享目录中，许多人可以同时访问它们。

GnuWin32安装说明

下载并执行exe(它来自SourceForge网站)指向一个合适的目录(我将使用C:\bin)。它会在那里创建一个GetGnuWin32目录，你将在其中运行download.bat，然后是install.bat(不带参数)，之后会有一个C:\bin\GetGnuWin32\gnuwin32\bin目录，这是Windows机器上曾经存在过的最有用的文件夹。将该目录添加到路径中，就可以开始了。

握

Select-String cmdlet和-match操作符使用正则表达式。此外，您还可以直接使用. net的正则表达式支持来实现更高级的功能。

排序

sort - object更强大(比我记得*nix的sort更强大)。允许对任意表达式进行多级排序。在这里，PowerShell对底层类型的维护有所帮助;例如，DateTime属性将被排序为DateTime，而不必确保格式化为可排序的格式。

uniq

Select-Object独特

Perl (PowerShell的功能有多接近Perl ?)

就Perl领域特定支持库的广度而言:还远远不及(目前)。

对于通用编程来说，PowerShell当然更具有内聚性和一致性，也更容易扩展。文本修改的一个缺口相当于Perl的。操作符。

哗啦��

自从使用AWK以来已经足够长了(肯定是>18年了，因为后来我只使用Perl)，所以不能真正评论。

赛德

(见上图)

File(提供文件信息的命令)

PowerShell的优势并不在于它可以对文件系统对象做什么(它在这里获得了全部信息，dir返回FileInfo或FolderInfo对象)，而是它是整个提供者模型。

您可以将注册表、证书存储、SQL Server、Internet Explorer的RSS缓存等视为对象空间，可以通过与文件系统相同的cmdlet进行导航。

PowerShell绝对是Windows的发展方向。微软已经将其列为未来非家用产品的要求之一。因此在Exchange中有丰富的支持，在SQL Server中有支持。这个只会膨胀。

最近的一个例子是TFS PowerToys。许多TFS客户端操作都不需要每次启动tf.exe(这需要一个新的TFS服务器连接等)，并且更容易进一步处理数据。以及允许广泛访问整个TFS客户端API，以比在TF.exe的任何团队资源管理器中公开的更详细的信息。

我直到最近才开始认真地接触PowerShell。尽管在过去的7年里，我一直在一个几乎完全基于Windows的环境中工作，但我有Unix背景，我发现自己一直在努力将我在Windows上的交互体验“Unix化”。至少可以说，这令人沮丧。

将PowerShell与Bash、tcsh或zsh这样的东西进行比较是公平的，因为grep、sed、awk、find等实用程序严格来说都不是shell的一部分;然而，它们将永远是任何Unix环境的一部分。也就是说，像Select-String这样的PowerShell命令具有与grep非常相似的功能，并且被捆绑为PowerShell的核心模块…所以界限可能有点模糊。

我认为最关键的是文化，而事实上，各自的工具集将体现各自的文化:

Unix is a file-based, (in general, non Unicode) text-based culture. Configuration files are almost exclusively text files. Windows, on the other hand has always been far more structured in respect of configuration formats--configurations are generally kept in proprietary databases (e.g., the Windows registry) which require specialised tools for their management. The Unix administrative (and, for many years, development) interface has traditionally been the command line and the virtual terminal. Windows started off as a GUI and administrative functions have only recently started moving away from being exclusively GUI-based. We can expect the Unix experience on the command line to be a richer, more mature one given the significant lead it has on PowerShell, and my experience matches this. On this, in my experience: The Unix administrative experience is geared towards making things easy to do in a minimal amount of key strokes; this is probably as a result of the historical situation of having to administer a server over a slow 9600 baud dial-up connection. Now PowerShell does have aliases which go a long way to getting around the rather verbose Verb-Noun standard, but getting to know those aliases is a bit of a pain (anyone know of something better than: alias | where {$_.ResolvedCommandName -eq "<command>"}?). An example of the rich way in which history can be manipulated: iptables commands are often long-winded and repeating them with slight differences would be a pain if it weren't for just one of many neat features of history manipulation built into Bash, so inserting an iptables rule like the following: iptables -I camera-1-internet -s 192.168.0.50 -m state --state NEW -j ACCEPT a second time for another camera ("camera-2"), is just a case of issuing: !!:s/-1-/-2-/:s/50/51 which means "perform the previous command, but substitute -1- with -2- and 50 with 51. The Unix experience is optimised for touch-typists; one can pretty much do everything without leaving the "home" position. For example, in Bash, using the Emacs key bindings (yes, Bash also supports vi bindings), cycling through the history is done using Ctrl-P and Ctrl-N whilst moving to the start and end of a line is done using Ctrl-A and Ctrl-E respectively ... and it definitely doesn't end there. Try even the simplest of navigation in the PowerShell console without moving from the home position and you're in trouble. Simple things like versatile paging (a la less) on Unix don't seem to be available out-of-the-box in PowerShell which is a little frustrating, and a rich editor experience doesn't exist either. Of course, one can always download third-party tools that will fill those gaps, but it sure would be nice if these things were just "there" like they are on pretty much any flavour of Unix. The Windows culture, at least in terms of system API's is largely driven by the supporting frameworks, viz., COM and .NET, both of-which are highly structured and object-based. On the other hand, access to Unix APIs has traditionally been through a file interface (/dev and /proc) or (non-object-oriented) C-style library calls. It's no surprise then that the scripting experiences match their respective OS paradigms. PowerShell is by nature structured (everything is an object) and Bash-and-friends file-based. The structured API which is at the disposal of a PowerShell programmer is vast (essentially matching the vastness of the existing set of standard COM and .NET interfaces).

简而言之，尽管PowerShell的脚本功能可以说比Bash更强大(特别是当您考虑到. net BCL的可用性时)，但交互体验明显较弱，特别是如果您从完全由键盘驱动、基于控制台的角度(就像许多unix用户一样)进行交互时。

这里有很多很棒的答案，这是我的看法。PowerShell是准备好了，如果你是…例子:

grep = "Select-String -Pattern"

sort = " sort - object "

uniq = "Get-Unique"

file = "Get-Item"

cat = "Get-Content"

Perl/AWK/Sed不是命令，而是实用程序，因此很难比较，但在PowerShell中几乎可以做所有事情。

我还没有看到PowerShell真正流行起来，至少现在还没有。因此，除非团队中的其他人已经知道它，否则学习它可能不值得。

对于您的困境，您最好使用其他人可以支持的脚本语言，如您提到的Perl或Ruby或Python。

我认为这在很大程度上取决于你需要做什么。就我个人而言，我一直在为自己的个人脚本使用Python，但我知道当我开始编写一些东西时，我永远无法将其传递下去——所以我尽量不做任何太有革命性的事情。