Live data from Hacker News

Bash and Windows Subsystem for Linux Demo [video]

channel9.msdn.com

281–290 of 316 posts

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

#281
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…

Cygwin has its own ANSI/VT100 emulation which is translated to Console API calls.

In the Cygnal project (http://www.kylheku.com/cygnal) I made a few fixes to this code.

With Cygnal you can write a terminal-oriented application using termios and VT100 escape sequences (or a library like ncurses if you wish). You just package it with the cygnal DLL, and any other DLL's. It will run fine in the console window.

For a demo of this, download the Windows installer for the TXR language.

https://bintray.com/kazinator/Binaries/TXR/txr-169

The txr.exe executable happily runs out of the cmd.exe console window with history, multi-line editing, etc. There is not a shred of Win32 code in TXR: it's just (a much enhanced fork of) the Linenoise library which uses termios and ANSI codes. Not a single #ifdef WIN32 in there.

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

#282

Earlier quoted context omitted.

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? :)

Why someone might use Wine is that it's free software. That's about it.

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

#284
post #123
post #121

Earlier quoted context omitted.

So VS can do C/C++ compilation now. I wonder if they will extend VS to work with other higher-level languages like Ruby and Python (et. al.) ? It would be nice to work from Windows but build for Linux that way, for other languages too.

Uh.... VS has always been able to do C/C++ compilation. Like... for decades now? Just not with the standard Linux toolchain, but you've always been able to build C/C++ projects on Windows.

Thanks for the downvote guys. I wasn't born under a rock.

The article was talking about Windows Subsystem for Linux, and my comment was that VS can do C/C++ for Linux. I thought that was implied by the context.

Anyways, I know VS has done C/C++ for forever. :)

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

#285
post #121
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…

So VS can do C/C++ compilation now. I wonder if they will extend VS to work with other higher-level languages like Ruby and Python (et. al.) ? It would be nice to work from Windows but build for Linux that way, for other languages too.

In case the context didn't make it obvious... I know that VS is based on, and can do compilation for C/C++. I was saying basically, "Oh cool. You can do VS compilation of C/C++ for Linux now. Do you plan in introducing it for other higher-level languages too? (Ruby, Python, et. al.)"

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

#286
post #230
post #188

Earlier quoted context omitted.

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.

People have been developing on OS X outside a VM for a while now, and OS X is most definitely not linux. If they can get WSL to be as linuxy as OS X (and arguably it's already close), Windows will be as good a dev platform for linux development as OS X. But they really need to fix notepad so it supports unix style line endings. That part of the demo was a bit embarrassing.

I love watching people developing on OS X, targeting Linux, without proper tests forgetting that Linux's FS's are by default case-sensitive in regards to file names, and completely forgetting that OS-X is case-insensitive, by default (and recommended to remain so, because most OS-X software is not developed with case-sensitive file-system awareness.)

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

#287
post #230

Earlier quoted context omitted.

People have been developing on OS X outside a VM for a while now, and OS X is most definitely not linux. If they can get WSL to be as linuxy as OS X (and arguably it's already close), Windows will be as good a dev platform for linux development as OS X. But they really need to fix notepad so it supports unix style line endings. That part of the demo was a bit embarrassing.

WSL is more Linuxy than macOS, it implements the Linux syscall interface rather than Darwin's.

I've been using WSL since it was released to the fast insider ring. It's pretty slick. There have been some warts and growing pains, but the team has been very responsive to bug reports. I've seen responses as quickly as 2 public build cycles (about a week) to get a fix for an issue reported on their github site.

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

#288

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 familiar with Elixir or Debootstrap (I'm guessing web-oriented)? But, I've had great success with using WSL for C++ oriented projects, building with both g++ & clang. Only issue in that regard I've had is that the emulated syscalls cannot currently enumerate ethernet devices. The calls are implemented, but fail at runtime currently. I've not yet filed a bug report, because I don't know how it should perform.

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

#289
post #9

Earlier quoted context omitted.

> - Visual Studio can compile with GNU/Linux C/C++ tools, gdb, linker etc First VS Core, now VS proper. Impressive! (going back to my ddd window on Linux, crying a bit inside).

A properly configured and well-curated collection of packages will yield an exceptional experience using emacs - if you're into that kind of thing. Add in some custom elisp and you're well on your way to a fully customizable development environment.

Are you talking about proper, legit Intellisense in Emacs? If so, I'm sold. More details?

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

#290

Earlier quoted context omitted.

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? :)

> less overhead

is it really? last time I read tests WSL was slower than VMs

Post reply on HN