<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ygra</author><text>&amp;gt; Don&amp;#x27;t know if it&amp;#x27;s any good --- never tried it; it says it&amp;#x27;s about half complete, but I don&amp;#x27;t know if it&amp;#x27;s a useful half.&lt;p&gt;There are at least two parties working on it who have interest in certain features to be working: It&amp;#x27;s the NuGet shell within MonoDevelop, so custom PowerShell hosts need to work as well as a bunch of things needed by NuGet. Then one of the more prolific developers actually gets paid to work on Pash to support features related to PowerShell add-ins and a few others. (My own efforts so far were mostly bits and pieces, missing cmdlets (there are still a lot of those), test cases, and weird parser behaviour, mostly due to my history of golfing in PowerShell – golfed code makes for some fun tests of edge cases.)</text><parent_chain><item><author>david-given</author><text>I did find an open source implementation here:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;pash.sourceforge.net&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;pash.sourceforge.net&amp;#x2F;&lt;/a&gt;&lt;p&gt;Don&amp;#x27;t know if it&amp;#x27;s any good --- never tried it; it says it&amp;#x27;s about half complete, but I don&amp;#x27;t know if it&amp;#x27;s a useful half.&lt;p&gt;After looking at the docs, you could do a lot of what Powershell does with Unix shells; you&amp;#x27;d need a different set of conventions, where instead of using unformatted text as an intermediate format you used a streamable table format with support for metadata. Then you could have commands like &amp;#x27;where&amp;#x27;, which would be awesome.&lt;p&gt;$ xps | xwhere user -eq dg | xsort -desc rss | xtop 10 | xecho &amp;quot;rss=@.rss cmdline=@.command&amp;quot;&lt;p&gt;...or something. sh syntax is a bit lacking; PowerShell&amp;#x27;s got lots of useful builtins, including having native support for the format so it knows how to present it to the user. An sh version would conversion routines back and forth from text.&lt;p&gt;The tricky part would be bootstrapping; getting enough functionality quickly enough that enough people would start using it to make it sustainable.&lt;p&gt;I&amp;#x27;d still rather use this than faff around with awk, though. I&amp;#x27;ve done way too much of that. And if I never have to parse the output of ls -l using cut again, I will be a happy person.</text></item><item><author>wumbernang</author><text>Couldn&amp;#x27;t agree more.&lt;p&gt;As a die hard Unix guy and ex Slashdot-esque zealot (colloquially a bit of a twat). Yet I&amp;#x27;m knocking out PowerShell all the time now and dread having to log into the pile of CentOS kit I have lying around. It is arcane. Even after 15 years I spend most of my time in the manpages or working out another damn config format.&lt;p&gt;Literally did a two liner to scrape a web page, parse it and call a REST endpoint with the parsed data as JSON in PowerShell. I cant even use python now. I&amp;#x27;ve been broken.&lt;p&gt;It makes me cringe saying all this as well kind of like a racist making amends with his past.&lt;p&gt;The only thing I still hate is windows update.</text></item><item><author>halo</author><text>&amp;gt;Wishlist: tmux, emacs, vi, netcat, shell option for vi-mode, rc-file with preferences, ncurses library, something simpler than curses, zip and unzip&lt;p&gt;No thankyou. I can certainly understand including SSH support, but I don&amp;#x27;t want what is pretty much the only remaining viable non-Unix platform to start bundling horribly dated and clunky Unix-like commands and bloated GNU tools.</text></item><item><author>cturner</author><text>For all Balmer&amp;#x27;s thing of dancing on a stage and chanting &amp;quot;developers&amp;quot;, there was no point under Gates or he at which Microsoft felt like a pro-developer company.&lt;p&gt;That has completely changed in the last eighteen months. Each time I think &amp;quot;wouldn&amp;#x27;t it be cool if&amp;quot; I&amp;#x27;m finding a few weeks later that someone at Microsoft is well ahead of me. How much easier it will be to ship my sucky roguelikes to Windows users in this new world!&lt;p&gt;Hmm. They can now have a path to obsolete cmd. As long as they ship a decent ssh client with the system, users will become accustomed to ssh-ing to their own box instead of using cmd.&lt;p&gt;Wishlist: tmux, emacs, vi, netcat, shell option for vi-mode, rc-file with preferences, ncurses library, something simpler than curses, zip and unzip. 256 colour is fine, although 24-bit would be impressive. &amp;#x2F;proc would be cool, but also a big ask I assume. They already have a strong compiler. Make it really easy to find the hex fingerprint required to log on to the sshd-server. Something like inetd could be useful, too.</text></item></parent_chain></comment><story><title>Looking Forward: Support for Secure Shell</title><url>http://blogs.msdn.com/b/looking_forward_microsoft__support_for_secure_shell_ssh1/archive/2015/06/02/managing-looking-forward-microsoft-support-for-secure-shell-ssh.aspx</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>emmelaich</author><text>There&amp;#x27;s also &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.lbreyer.com&amp;#x2F;xml-coreutils.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.lbreyer.com&amp;#x2F;xml-coreutils.html&lt;/a&gt; which is interesting.&lt;p&gt;But I&amp;#x27;ve never tried it; just came across it recently as a homebrew update.</text><parent_chain><item><author>david-given</author><text>I did find an open source implementation here:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;pash.sourceforge.net&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;pash.sourceforge.net&amp;#x2F;&lt;/a&gt;&lt;p&gt;Don&amp;#x27;t know if it&amp;#x27;s any good --- never tried it; it says it&amp;#x27;s about half complete, but I don&amp;#x27;t know if it&amp;#x27;s a useful half.&lt;p&gt;After looking at the docs, you could do a lot of what Powershell does with Unix shells; you&amp;#x27;d need a different set of conventions, where instead of using unformatted text as an intermediate format you used a streamable table format with support for metadata. Then you could have commands like &amp;#x27;where&amp;#x27;, which would be awesome.&lt;p&gt;$ xps | xwhere user -eq dg | xsort -desc rss | xtop 10 | xecho &amp;quot;rss=@.rss cmdline=@.command&amp;quot;&lt;p&gt;...or something. sh syntax is a bit lacking; PowerShell&amp;#x27;s got lots of useful builtins, including having native support for the format so it knows how to present it to the user. An sh version would conversion routines back and forth from text.&lt;p&gt;The tricky part would be bootstrapping; getting enough functionality quickly enough that enough people would start using it to make it sustainable.&lt;p&gt;I&amp;#x27;d still rather use this than faff around with awk, though. I&amp;#x27;ve done way too much of that. And if I never have to parse the output of ls -l using cut again, I will be a happy person.</text></item><item><author>wumbernang</author><text>Couldn&amp;#x27;t agree more.&lt;p&gt;As a die hard Unix guy and ex Slashdot-esque zealot (colloquially a bit of a twat). Yet I&amp;#x27;m knocking out PowerShell all the time now and dread having to log into the pile of CentOS kit I have lying around. It is arcane. Even after 15 years I spend most of my time in the manpages or working out another damn config format.&lt;p&gt;Literally did a two liner to scrape a web page, parse it and call a REST endpoint with the parsed data as JSON in PowerShell. I cant even use python now. I&amp;#x27;ve been broken.&lt;p&gt;It makes me cringe saying all this as well kind of like a racist making amends with his past.&lt;p&gt;The only thing I still hate is windows update.</text></item><item><author>halo</author><text>&amp;gt;Wishlist: tmux, emacs, vi, netcat, shell option for vi-mode, rc-file with preferences, ncurses library, something simpler than curses, zip and unzip&lt;p&gt;No thankyou. I can certainly understand including SSH support, but I don&amp;#x27;t want what is pretty much the only remaining viable non-Unix platform to start bundling horribly dated and clunky Unix-like commands and bloated GNU tools.</text></item><item><author>cturner</author><text>For all Balmer&amp;#x27;s thing of dancing on a stage and chanting &amp;quot;developers&amp;quot;, there was no point under Gates or he at which Microsoft felt like a pro-developer company.&lt;p&gt;That has completely changed in the last eighteen months. Each time I think &amp;quot;wouldn&amp;#x27;t it be cool if&amp;quot; I&amp;#x27;m finding a few weeks later that someone at Microsoft is well ahead of me. How much easier it will be to ship my sucky roguelikes to Windows users in this new world!&lt;p&gt;Hmm. They can now have a path to obsolete cmd. As long as they ship a decent ssh client with the system, users will become accustomed to ssh-ing to their own box instead of using cmd.&lt;p&gt;Wishlist: tmux, emacs, vi, netcat, shell option for vi-mode, rc-file with preferences, ncurses library, something simpler than curses, zip and unzip. 256 colour is fine, although 24-bit would be impressive. &amp;#x2F;proc would be cool, but also a big ask I assume. They already have a strong compiler. Make it really easy to find the hex fingerprint required to log on to the sshd-server. Something like inetd could be useful, too.</text></item></parent_chain></comment><story><title>Looking Forward: Support for Secure Shell</title><url>http://blogs.msdn.com/b/looking_forward_microsoft__support_for_secure_shell_ssh1/archive/2015/06/02/managing-looking-forward-microsoft-support-for-secure-shell-ssh.aspx</url></story>