←back to thread

Ubuntu on Windows

(blog.dustinkirkland.com)
2049 points bpierre | 2 comments | | HN request time: 0.409s | source
1. justncase80 ◴[] No.11391831[source]
This is great.

For the last couple of years, as a windows user, I have just been installing Git Scm, which includes something similar to this and have been using that for all script / command line needs.

If this was baked into Windows so much the better! I would love it if nobody ever wrote a single CMD or PS1 file ever again. Let's please all just converge on bash and put this debate behind us.

replies(1): >>11417487 #
2. JdeBP ◴[] No.11417487[source]
> Let's please all just converge on bash

As (I hope most) Unix/Linux users would respond: let's not.

A good thing about the Unix/Linux world is that there is a multiplicity of shells. And this is regularly taken advantage of. I have systems (for example) where my interactive shell is the Z shell and /bin/sh is the Almquist shell. I have others where /bin/sh is the Korn shell.

The "Shellshock" incident should have told everyone that Bourne Again shell everywhere, for everything, is not a good idea.

In any case, this is not a debate to be won/lost in the first place, as I hope Unix/Linux users would also respond. There are places for shell scripts, places for Python, places for perl, places for awk, TCL, REXX, execlineb, and a whole lot of others. One size, one scripting language, does not fit all.

Indeed, if you do eventually gain all the Ubuntu command-line toolsets from this, your options should broaden to those and more besides, not narrow to the Bourne Again shell.