Earlier quoted context omitted.
Cutting them some slack I think is not bad idea. They are literally integrating two big operating system together. Do you see what I am saying? As we all know Microsoft messed up with mobile and web, but when it comes to software development they are ruler without even competition. Windows kernel is wonderful peace of software, and with this wsl they are literally showing industry how is software developed.
I will, they've been clear about it being a work in progress. There are a lot of other people saying how amazing it is though, when functionality wise it's only just coming up to par with cygwin. Edit - functionality wise as a usable bash shell, it's an acceptable linux virtual machine already.
Invoke Win32 applications with Bash on Windows
11–20 of 52 posts
Re: Invoke Win32 applications with Bash on Windows
#12Wow, this is really impressive. Last time I worked with bash on Windows it felt like isolated island. But with this. I think it is a viable option right now. The only down side to it is slow file system operations. Compiling a single toy kernel (xv6) would take much longer than Linux. This is amazing, now I can have emacs server in Linux running through bash with windows service manager. This is fucking awesome. I ho…
Re: Invoke Win32 applications with Bash on Windows
#13Re: Invoke Win32 applications with Bash on Windows
#14This finally makes bash on windows functional. It was one of its limitations that made it feel disconnected from the rest of Windows.
Re: Invoke Win32 applications with Bash on Windows
#15Earlier quoted context omitted.
Cutting them some slack I think is not bad idea. They are literally integrating two big operating system together. Do you see what I am saying? As we all know Microsoft messed up with mobile and web, but when it comes to software development they are ruler without even competition. Windows kernel is wonderful peace of software, and with this wsl they are literally showing industry how is software developed.
I will, they've been clear about it being a work in progress. There are a lot of other people saying how amazing it is though, when functionality wise it's only just coming up to par with cygwin. Edit - functionality wise as a usable bash shell, it's an acceptable linux virtual machine already.
Also, not being able to edit the WSL filesystem from inside a windows editor is a huge loss in terms of usage. It's worse than using Samba/CIFS to share a directory and edit across to a full VM. I happen to like my gui editor, but prefer to run in Linux.
Re: Invoke Win32 applications with Bash on Windows
#16Earlier quoted context omitted.
I will, they've been clear about it being a work in progress. There are a lot of other people saying how amazing it is though, when functionality wise it's only just coming up to par with cygwin. Edit - functionality wise as a usable bash shell, it's an acceptable linux virtual machine already.
It is not a virtual machine and doesn't involve Linux in any way. It is an implementation of the Linux syscalls for the Windows kernel.
Re: Invoke Win32 applications with Bash on Windows
#17This finally makes bash on windows functional. It was one of its limitations that made it feel disconnected from the rest of Windows.
It also introduces potentially significant new attack surface.
Plus Bash on Windows isn't a new thing: we already have Cygwin, MinGW and I believe there was also some native Windows PE ports too. This is just a better implementation than the aforementioned three.
Re: Invoke Win32 applications with Bash on Windows
#18Wow, this is really impressive. Last time I worked with bash on Windows it felt like isolated island. But with this. I think it is a viable option right now. The only down side to it is slow file system operations. Compiling a single toy kernel (xv6) would take much longer than Linux. This is amazing, now I can have emacs server in Linux running through bash with windows service manager. This is fucking awesome. I ho…
Actually,what does an emacs server running in wsl get you rather than just running the standard win32 build?