http://thomasfreudenberg.com/blog/archive/tags/Monad/default.aspxTags: MonadenCommunityServer 2007.1 (Build: 20917.1142)http://thomasfreudenberg.com/blog/archive/2006/04/25/The-shell-formerly-known-as-monad.aspxTue, 25 Apr 2006 12:11:00 GMT483d7ed9-aa38-4432-af18-89f61e4445bf:15211Thomas Freudenberg1http://thomasfreudenberg.com/blog/rsscomments.aspx?PostID=15211http://thomasfreudenberg.com/blog/commentapi.aspx?PostID=15211http://thomasfreudenberg.com/blog/archive/2006/04/25/The-shell-formerly-known-as-monad.aspx#comments<p>...is now called <a href="http://blogs.msdn.com/powershell/">Windows PowerShell</a> and available as <a href="http://blogs.msdn.com/powershell/archive/2006/04/25/583344.aspx">RC1</a>.</p> <p><a href="http://blogs.msdn.com/heaths">Heath Stewart</a> says in his comment:</p><blockquote><p>I find this tedious. Typing &quot;cmd&quot; is so much better than &quot;command&quot; as we had to in Windows 9x, just as &quot;msh&quot; is so much better than typing &quot;powershell&quot;. The more generalized &quot;Microsoft Shell&quot; sounds prominant, like &quot;korn shell&quot; and &quot;bash shell&quot;. &quot;PowerShell&quot; just sounds like too much of a buzzword, and buzzwords don&#39;t tend to last.</p></blockquote><p>I agree on him. I guess I&#39;ll continue saying Monad as I&#39;m still saying Avalon, Indigo,... well, you name it.</p><p>BTW, did the marketing folks at Microsoft try <a rel="nofollow" href="http://www.google.com/search?q=powershell">Google</a> before picking PowerShell?</p><img src="http://thomasfreudenberg.com/aggbug.aspx?PostID=15211" width="1" height="1">DevelopmentPowerShellMonad