您还可以尝试使用BashWin at在Windows上运行Bash脚本 https://github.com/skanga/BashWin。

我已经使用了一些PowerShell来实现脚本自动化。虽然环境看起来比Unix shell考虑得更周到，但实际上使用对象而不是文本流要笨拙得多，而且过去30年开发的许多Unix设施仍然缺失。

Cygwin仍然是我在Windows主机上选择的脚本环境。在完成任务方面，它肯定胜过其他选择。

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机器上曾经存在过的最有用的文件夹。将该目录添加到路径中，就可以开始了。

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

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

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

我直到最近才开始认真地接触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用户一样)进行交互时。

作为一个从1997年到2010年专注于Windows企业开发的人，显而易见的答案是PowerShell，因为前面给出的所有好的理由(例如，它是微软企业战略的一部分;与Windows/COM/.NET集成良好;使用对象而不是文件提供了一个“更丰富的”编码模型)。出于这个原因，我在过去两年左右的时间里一直在使用和推广PowerShell，并明确地相信我是在遵循“比尔之言”。

然而，作为一个实用主义者，我不再确定PowerShell是一个很好的答案。虽然这是一款出色的Windows工具，并且为填补Windows命令行这一历史性的漏洞提供了非常必要的一步，但我们都看到微软对消费者计算的控制正在下滑，微软似乎越来越有可能面临一场大规模的战斗，以保持其操作系统对未来企业的重要性。

事实上，鉴于我发现我的工作越来越多地处于不同的环境中，我发现目前使用Bash脚本要有用得多，因为它们不仅可以在Linux、Solaris和Mac OS X上工作，而且还可以在cygwin的帮助下在Windows上工作。

因此，如果您相信操作系统的未来是商品化的，而不是垄断的，那么选择一种灵活的开发工具策略，在可行的情况下远离专有工具似乎是有意义的。然而，如果你认为你的未来被所有的雷德蒙德所主宰，那么就选择PowerShell吧。