<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc=" http://purl.org/dc/elements/1.1/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>briancarper.net (λ) (Tag: Powershell)</title><link>http://briancarper.net/tag/62/powershell</link><description>Some guy's blog about programming and Linux and cows.</description><item><title>Windows Powershell: Can you handle the power?</title><link>http://briancarper.net/blog/windows-powershell-can-you-handle-the-power</link><guid>http://briancarper.net/blog/windows-powershell-can-you-handle-the-power</guid><pubDate>Sat, 15 Aug 2009 14:50:38 -0700</pubDate><description>&lt;p&gt;MS Powershell is Microsoft's ripoff of Bash.  I don't think this is a bad thing necessarily.  Bash is a good tool and it's open source.  If Windows bundled a sensible, full-fledged Bash and got rid of CMD.EXE I would dance for joy.&lt;/p&gt;

&lt;p&gt;So Powershell lets you refer to your home directory as &lt;code&gt;~&lt;/code&gt; and a bunch of commands have *nix aliases like &lt;code&gt;ls&lt;/code&gt; and &lt;code&gt;cat&lt;/code&gt;.  This is nice for those who have *nix commands firmly internalized.  You have to use &lt;code&gt;.\foo.bat&lt;/code&gt; to run things in the current directory instead of just &lt;code&gt;foo.bat&lt;/code&gt;, which I thought was cool.&lt;/p&gt;

&lt;p&gt;But Powershell is not without its problems.  For one thing I see this a lot:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;The redirection operator '&amp;lt;' is not supported yet.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;How hard is it to implement input redirection, really?  For another thing, tab completion continues to be broken.  When you hit &lt;code&gt;Tab&lt;/code&gt; it still doesn't put a slash at the end of the text it inserts.  You have to type a manual &lt;code&gt;\&lt;/code&gt; every time you hit &lt;code&gt;Tab&lt;/code&gt;, to continue tabbing your way through directories.  Thus doubling the number of keystrokes you're forced to type.  This continues to drive me crazy.  There's a &lt;a href=&quot;http://www.eggheadcafe.com/conversation.aspx?messageid=29874884&amp;amp;threadid=29852783&quot;&gt;small amount of evidence&lt;/a&gt; that someday it'll be fixed, but I'm not holding my breath.&lt;/p&gt;

&lt;p&gt;You also usually can't bundle flags together.  e.g. &lt;code&gt;rm -rf&lt;/code&gt; would have to be &lt;code&gt;rm -r -f&lt;/code&gt; in Powershell.  This is just annoying enough to bother me, but I can look past it.&lt;/p&gt;

&lt;p&gt;Sadly, Powershell also runs slower than a geriatric sea turtle.  I don't understand what it's doing that takes 10-20 seconds to startup.  Or why tab completion often lags for 5+ seconds itself.  &lt;/p&gt;

&lt;p&gt;My happiest surprise was when I tried to uninstall Powershell (so I could try version 2) and got this:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/random/powershell.png&quot; alt=&quot;/random/powershell.png&quot; title=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p&gt;This dialog listed every program installed on my computer (in random order) including every Windows Update I'd ever installed.  The worst part is that I couldn't even dismiss this dialog as an error.  For all I know, uninstalling Powershell &lt;em&gt;could&lt;/em&gt; cause every program on my computer to stop working.  I've seen stranger things happen in Windows.&lt;/p&gt;

&lt;p&gt;A person walking past my office when I saw this would have heard the crazed, maniacal, tortured laughter that only the experience of being forced to use Windows can elicit.&lt;/p&gt;</description></item></channel></rss>

