<story><title>The Dune Shell</title><url>https://adam-mcdaniel.github.io/dune-website/</url></story><parent_chain><item><author>xelamonster</author><text>It&amp;#x27;s also just absurdly verbose for a language intended mainly for manual input. I get annoyed having to type out `sudo systemctl` multiple times in a row, in Powershell every single command is at minimum that long. Which makes it way more difficult to memorize the commands too.</text></item><item><author>Brian_K_White</author><text>The problem of powershell is not merely thet it&amp;#x27;s new and different, and not merely that you have to learn a new and different way to get a given task done.&lt;p&gt;Powershell makes some things possible or easier that weren&amp;#x27;t possible or easy, but only at the expense of making other things either impossible or at least vastly less practical, and all in all it&amp;#x27;s a bad trade off and a wrong set of priorities for the job it claims to fill, or at least for the job bash currently fills. It&amp;#x27;s not that bash is a gold standard, just that it&amp;#x27;s not &lt;i&gt;fundamentally wrong&lt;/i&gt;.</text></item><item><author>hi-v-rocknroll</author><text>I like the ideas of Dune and Nu, which I think were trailblazed by powershell to a degree. The problems of pure *NIX pipe philosophy with text as the lingua franca were persistent parsing problems and escaping. However, the problems of going to far in the way powershell went was it was too radical having to reimagine&amp;#x2F;replace&amp;#x2F;relearn almost everything, and generally more difficult to accomplish simple text manipulation. Nu at least maintains most of the *NIX shell UX. Maybe at some point in the future, we will reach parity to where there will fusion of the main DSLs, shells, and programming languages into a runtime interaction system that is somewhere between psql, Erlang shell, nu, and Squeak where there is programming language-OS parity obliterating the distinctions between programming languages, command shells, and DBMS shells. One can dream of a future where perhaps it will be possible to write a function, library, or program in any language one chooses and call it from any other shell or language without swig or ceremony.</text></item></parent_chain><comment><author>WorldMaker</author><text>There are ton of aliases. It&amp;#x27;s &amp;quot;impolite&amp;quot; [0] to use aliases in scripts and documentation so looking at PowerShell examples is way more verbose than actually using it day to day in a REPL. Sure I could write `Set-Location` a million times a day, but I just use `cd` in the old ways. Same with `Get-ChildItem`, I tend to just use `ls` myself because of ancient habits. (I find it interesting how many have been moving to `gci` instead as the more PowerShell-native `ls` alias. I&amp;#x27;ve not been convinced to do that myself, but I think it has to do with `gci` is way more powerful than most shells&amp;#x27; `ls` and is used to navigate everything from folder structures to object structures including that its not a bad `jq` if you convert JSON files to PowerShell objects.)&lt;p&gt;[0] It&amp;#x27;s from a version of the Python ethos that code is read way more often than it is written, so when you are polishing PowerShell code to share with others you expand all the aliases so that it is easier to read.</text></comment>
<story><title>The Dune Shell</title><url>https://adam-mcdaniel.github.io/dune-website/</url></story><parent_chain><item><author>xelamonster</author><text>It&amp;#x27;s also just absurdly verbose for a language intended mainly for manual input. I get annoyed having to type out `sudo systemctl` multiple times in a row, in Powershell every single command is at minimum that long. Which makes it way more difficult to memorize the commands too.</text></item><item><author>Brian_K_White</author><text>The problem of powershell is not merely thet it&amp;#x27;s new and different, and not merely that you have to learn a new and different way to get a given task done.&lt;p&gt;Powershell makes some things possible or easier that weren&amp;#x27;t possible or easy, but only at the expense of making other things either impossible or at least vastly less practical, and all in all it&amp;#x27;s a bad trade off and a wrong set of priorities for the job it claims to fill, or at least for the job bash currently fills. It&amp;#x27;s not that bash is a gold standard, just that it&amp;#x27;s not &lt;i&gt;fundamentally wrong&lt;/i&gt;.</text></item><item><author>hi-v-rocknroll</author><text>I like the ideas of Dune and Nu, which I think were trailblazed by powershell to a degree. The problems of pure *NIX pipe philosophy with text as the lingua franca were persistent parsing problems and escaping. However, the problems of going to far in the way powershell went was it was too radical having to reimagine&amp;#x2F;replace&amp;#x2F;relearn almost everything, and generally more difficult to accomplish simple text manipulation. Nu at least maintains most of the *NIX shell UX. Maybe at some point in the future, we will reach parity to where there will fusion of the main DSLs, shells, and programming languages into a runtime interaction system that is somewhere between psql, Erlang shell, nu, and Squeak where there is programming language-OS parity obliterating the distinctions between programming languages, command shells, and DBMS shells. One can dream of a future where perhaps it will be possible to write a function, library, or program in any language one chooses and call it from any other shell or language without swig or ceremony.</text></item></parent_chain><comment><author>Vegenoid</author><text>IMO, getting comfortable with and tuning autocomplete makes this a non-issue, and the benefit of the verbose commands is that they are very discoverable.</text></comment>