Live data from Hacker News

Bash and Windows Subsystem for Linux Demo [video]

channel9.msdn.com

211–220 of 316 posts

Re: Bash and Windows Subsystem for Linux Demo [video]

#211
post #188

Earlier quoted context omitted.

For this reason, whenever I try to develop anything on Windows, especially systems related stuff, I will do so in a VM. I may develop a test suite and try running it on Windows, but the Windows Linux Subsystem will never be reliable to me, until it aims to guarantee 100% compatibly.

Bash and Windows Subsystem for Linux is a band-aid solution for a fundamental problem for Microsoft: Linux tooling and kernel are IT industry standards.

They are for one part of the tech industry (which I count myself in) but it's pretty obvious that for many others, Microsoft-based tech (which now runs everywhere) is a standard. Why not persue both?

Re: Bash and Windows Subsystem for Linux Demo [video]

#212
post #143

Earlier quoted context omitted.

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.

See, that's not really what I see in my experience. About half of my friends that hack around use macOS, another half use Linux, and then a couple use Windows. 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.

I've interviewed at a couple local companies with 50+ devs each (mostly web dev positions), and almost everyone uses a Mac. This is anecdote of course, but I very rarely see devs using Linux professionally (natively, not in a VM).

That said, it depends on the kind of work; obviously, .NET developers almost exclusively use Windows, and I've noticed that sysadmins and system engineers are a little more likely to use Linux.

Re: Bash and Windows Subsystem for Linux Demo [video]

#213

Earlier quoted context omitted.

Why wouldn't getting as close to 100% compatibility as possible be the aim? WSL is currently beta. The installation documentation has a big warning at the top that functionality is currently incomplete.

All I can say is that the first two things I tried on the Windows Linux Subsystem didn't work, mainly running Elixir and Debootstrap. It's okay that they aren't (yet?) supported, but something that looks & smells like Ubuntu, yet isn't, doesn't inspire confidence that it can be trusted to act like Ubuntu. An alternative approach would be to call it Winbuntu, Winux, or simply Ubuntu for . Then aggressively maintain a…

I'm not sure a public-facing curated list of specific compatibility issues would be practical at this stage of the project's life; it's changing fairly rapidly. FWIW, the bug tracker is public, and the team seems to be fairly responsive; a UPX Compression bug I ran into was tagged fixinbound within a couple weeks. https://github.com/Microsoft/BashOnWindows

The speed at which they can push new builds to people who aren't on Windows Insider is a bit unfortunate, though.

Re: Bash and Windows Subsystem for Linux Demo [video]

#214
post #183

Earlier quoted context omitted.

That would be a huge regression. NT is far more advanced than Linux and BSD combined.

NT is basically OpenVMS. So it's about a decade more advanced than UNIX. Put like that, moving to UNIX would be a regression, but not a huge one. The Linux kernel is of about the same vintage as NT, though. And it's had a lot more work and public review done on it.

>NT is basically OpenVMS.

Well, that explains the PowerShell syntax.

Re: Bash and Windows Subsystem for Linux Demo [video]

#215

I 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…

I think the same. (Actually the title sounds like running Windows on Linux ;)) I'll be curious what happens - somehow I'm thinking they would be pretty stupid to do that. There is so much high end engineering and design software running on Windows only, they'd loose them all. On the other hand...does anyone need Windows except in the grey and boring high end/office section?

As a matter of fact, people are moving away since some time, either to Linux, macOS ooooor iOS/Android (haha). I guess even by economical means removing that lock-in may make sense.

Re: Bash and Windows Subsystem for Linux Demo [video]

#216
post #2

This 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…

Sorry for being dense but how is this better than running seamless window Linux under vmware? With that I can also access shared files, etc.

It's less overhead and better integrated into the system as a whole. After all a VM is still a separate entity in its own environment. WSL is jumping over the fence and runs Linux stuff in a Windows environment.

Think of it the other way. Why would you use wine if you could just run Windows in a VM? :)

Re: Bash and Windows Subsystem for Linux Demo [video]

#217

Earlier quoted context omitted.

That would be a huge regression. NT is far more advanced than Linux and BSD combined.

Source? Personally, I wonder how long it takes before redmond realizes that they are wasting shareholder money by maintaining/developing a proprietary kernel. It's not like they could not sell windows/linux as a perfectly good OS with copyrighted components on top of the kernel. Or then I have missed something significant.

how can they sell GPL OS? I mean they can try, but people will just download for free if they can.

Re: Bash and Windows Subsystem for Linux Demo [video]

#218

Earlier quoted context omitted.

The way I solved the terminal emulator shortcommings is this: Install a gtk-based terminal emulator with gtk/gnome dependencies on you ubuntu subsystem and run it with `DISPLAY=localhost:0.0` environment variable. This works if you run XServer Client on your Windows side. I use XcSrv and pantheon-terminal.

Konsole or yaquake are far better options

Those are pulling KDE dependencies? I didn't consider them as I already used GTK dependencies for rendering other software, so I wanted to stay on GTK stack.

Re: Bash and Windows Subsystem for Linux Demo [video]

#219

Earlier quoted context omitted.

> - vt sequences fixed (so stuff like colored output, midnight commander, etc work and the terminal doesn't screw up) Does this mean tmux will work?

I'll just leave this here: https://blogs.msdn.microsoft.com/commandline/2016/06/08/tmux... :)

I'll just leave this here: https://github.com/Microsoft/BashOnWindows/issues/406

Re: Bash and Windows Subsystem for Linux Demo [video]

#220
post #2

This 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…

Sorry for being dense but how is this better than running seamless window Linux under vmware? With that I can also access shared files, etc.

you don't pay for RAM that the VM doesn't use and don't have to deal with madness that is sharing files over sftp/smb/nfs/shared folders/etc.
Post reply on HN