The biggest problem I have with the WSL is that it is intrinsically tied to stable Windows releases; there is no way to get incremental updates for Bash on Windows unless you subscribe to the Windows Insider program, which is a way of running prerelease versions of Windows. So in order to get Linux features like inotify working you have to sacrifice the stability of your operating system. This looks like it'll be tru…
Output from `bash --version` on macOS: `GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16) Copyright (C) 2007 Free Software Foundation, Inc.` that's a 10yr old bash and there's barely any shell magic that you can do on Linux that won't work on macOS. And since by far most devs use macOS, most binaries support at least the macOS version of bash. All in all, no need to worry :p
Bash and Windows Subsystem for Linux Demo [video]
141–150 of 316 posts
Re: Bash and Windows Subsystem for Linux Demo [video]
#142Earlier quoted context omitted.
On their blog they state that raw sockets (ping), ip address / ip route will work.
Still some work there though. Traceroute errors with: setsockopt IP_MTU_DISCOVER: Protocol not available
We are, however, continuing to work on solving these and several other networking issues to close the gap in our networking support.
As a work-around, you could always call Windows' tracert.exe via the interop feature ;)
An if you're just using standard sockets technologies (e.g. HTTP, TLS, FTP, SSH, etc.) all should be good.
Re: Bash and Windows Subsystem for Linux Demo [video]
#143Earlier quoted context omitted.
Output from `bash --version` on macOS: `GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16) Copyright (C) 2007 Free Software Foundation, Inc.` that's a 10yr old bash and there's barely any shell magic that you can do on Linux that won't work on macOS. And since by far most devs use macOS, most binaries support at least the macOS version of bash. All in all, no need to worry :p
> by far most devs use macOS I'm not sure about this - that seems too extreme of a statement. If there is any winner, it's going to be Windows. IMO, Linux and macOS will be within 5 percentage points of each other. From what I've seen at university, it's something like 60% Windows, ~20% macOS, ~20% Linux (usually Ubuntu). Much more Linux/Mac in the "hackier" courses, usually with a slight majority to Macs. Where can…
Devs who write native apps for an OS (e.g. DirectX games for Windows) will of course use that OS.
Re: Bash and Windows Subsystem for Linux Demo [video]
#144This is coming to Windows stable in April: - vt sequences fixed (so stuff like colored output, midnight commander, etc work and the terminal doesn't screw up) - Elixir and Go work - Also Postgres and MySQL - You can launch Windows apps from bash. - inotify works - Visual Studio can compile with GNU/Linux C/C++ tools, gdb, linker etc There's some recent fast ring info on: https://blogs.msdn.microsoft.com/commandline/2…
Wow those are some pretty significant updates! I've loved the idea of bash-on-windows but it was missing just enough that it wasn't worth it moving away from my current love affair with the "git bash" system I'm using. With these changes, it looks like I'll be jumping ship when it comes to stable! Great work to everyone involved!
Re: Bash and Windows Subsystem for Linux Demo [video]
#145Running git-bash since 4 years ago. I hate cmd. Microsoft sucks. Windows13 will be based 100% based on Great Linux
>Windows13 will be based 100% based on Great Linux I want to believe. I'd go fucking apeshit if Windows dropped the NT kernel for Linux or BSD.
Re: Bash and Windows Subsystem for Linux Demo [video]
#146Earlier quoted context omitted.
> by far most devs use macOS I'm not sure about this - that seems too extreme of a statement. If there is any winner, it's going to be Windows. IMO, Linux and macOS will be within 5 percentage points of each other. From what I've seen at university, it's something like 60% Windows, ~20% macOS, ~20% Linux (usually Ubuntu). Much more Linux/Mac in the "hackier" courses, usually with a slight majority to Macs. Where can…
My impression is that most devs who write POSIX software these days use macOS (with possibly Linux running in a VM.) AFAIK, that's more to do with preferring Apple hardware, and then Linux not having 100% support for said hardware (e.g. touchpad multitouch / "force touch".) Devs who write native apps for an OS (e.g. DirectX games for Windows) will of course use that OS.
In general, I see Linux native used as often as Mac native, and Linux VMs used on Windows all the time. POSIX has little to do with it.
Re: Bash and Windows Subsystem for Linux Demo [video]
#147Re: Bash and Windows Subsystem for Linux Demo [video]
#148I Still wish they did the opposite. I want to seamlessly run an occasional windows app in linux, and I would pay for it. There is literally zero chance of me switching back to windows for day to day usage. Edit: idobai, I can't reply because your account is banned, but last I tried Wine and Crossover do not work for the apps I am trying to use. Edit 2: cyloneyes, you're banned too. But "They" would be Microsoft. They…
Re: Bash and Windows Subsystem for Linux Demo [video]
#149This should be really useful for people who are forced to use Windows (e.g. at work). Other than that, I don't think many Linux/Unix enthusiasts are looking forward to running a spyware-ridden closed-source non-Unix operating system.
Reposting a dead comment on this parent, because it's entirely reasonable. No, I believe they're not really after the enthusiasts. I think they're after the fence sitters. Implementing these tools on Windows removes motivation for casual dissenters from building intertia and leaving their platform. This is of course not the first time Microsoft has done something like this. Historically, step two is where they extend…
Re: Bash and Windows Subsystem for Linux Demo [video]
#150This should be really useful for people who are forced to use Windows (e.g. at work). Other than that, I don't think many Linux/Unix enthusiasts are looking forward to running a spyware-ridden closed-source non-Unix operating system.
Reposting a dead comment on this parent, because it's entirely reasonable. No, I believe they're not really after the enthusiasts. I think they're after the fence sitters. Implementing these tools on Windows removes motivation for casual dissenters from building intertia and leaving their platform. This is of course not the first time Microsoft has done something like this. Historically, step two is where they extend…