51–60 of 251 posts
Only thing I wish they could do is make calling Linux programs from Windows a bit more natural. Yeah "bash -c" works, but it's not exactly ideal.
Earlier quoted context omitted.
Microsoft adds this amazing set of features and the only response you have is "your name is insulting the people you're trying to appeal to"? "Trying"? As if they're failing? Do you know how much people love this project?
A lot of resistance some will have to WSL will be old battle scars from Microsofts past behaviour. Microsoft have done a lot over the years to troll the Linux community. While many of the younger HN members will be familiar with the "new open source Microsoft" some of us oldies have had to endure IE breaking the web plus ActiveX / Silverlight and other MS web lockins. Comments like "open source is communism" from top…
Whilst I really appreciate some of the things Microsoft is open sourcing I also find their current telemetry and privacy stance troubling.
Anyone tried deploying a linux program on windows via WSL?
Ok, this is awesome, if everything works as advertised. I have been mostly a Linux user for quite some time - at least on my own computer, clients always have Windows. But this year I bought a Surface Pro as a secondary device. I first evaluated WSL and really liked it, but I switched to Hyper+Git Bash because networking in node.js was not working properly, and because I could not start Windows programs from the comm…
Earlier quoted context omitted.
A lot of resistance some will have to WSL will be old battle scars from Microsofts past behaviour. Microsoft have done a lot over the years to troll the Linux community. While many of the younger HN members will be familiar with the "new open source Microsoft" some of us oldies have had to endure IE breaking the web plus ActiveX / Silverlight and other MS web lockins. Comments like "open source is communism" from top…
I also remember the standardization process of OOXML. https://en.wikipedia.org/wiki/Standardization_of_Office_Open... I also think their current strategy could be the one you describe. We're at the Embrace phase. It's not sure that Extend will follow but I wonder what it could look like. Maybe it will be something convenient you can do in Linux only if you're running it inside WSL. Given how Linux is used it should b…
Microsoft's revenue from patents collected from companies such as Samsung and HTC is like $1 billion.
Earlier quoted context omitted.
I recently tried starting Windows CLI programs from within bash and it worked just fine, but you have to specify the entire filename, like "./notepad.exe".
This is usually because, by default on many Linux flavours, the current directory is not included in your path environment variable.
Earlier quoted context omitted.
A lot of resistance some will have to WSL will be old battle scars from Microsofts past behaviour. Microsoft have done a lot over the years to troll the Linux community. While many of the younger HN members will be familiar with the "new open source Microsoft" some of us oldies have had to endure IE breaking the web plus ActiveX / Silverlight and other MS web lockins. Comments like "open source is communism" from top…
My remarks were directed at the product being discussed ("Bash on Windows"), a name that I think is incorrect for objective reasons. You can agree or disagree, but the comment was technical in nature, not trolling. People do not use "Bash on Windows" just for the sake of using Bash (the shell), they use it to access GNU/Linux software through the WSL ABI.
Speaking for myself, personally - if I want to run GNU/Linux software through the Linux ABI - I'm not going to be doing it on WSL - I'll do it on a VM or on a farm of VPS/EC2 instances somewhere. The attraction to me for WSL is the ability to have all my rich windows software, tools in the same environment that I'm connecting to those hosts from (which I normally do with OS X).
Note that the vast number of improvements (consoling, ping, vt100 support, launching windows apps from linux, etc...) in Creators Update are about improving the CLI/Shell experience for users.
Earlier quoted context omitted.
EDIT: Your choice of shell can be something different than bash... you opt to use zsh or fish or another shell. Therefore saying "Bash for Windows" can be objectively said to be unnecessarily confusing/inaccurate. I think Cygwin was less convenient than an ABI such as WSL, but by no means "terrible". Cygwin was initially released around 1995, it served a valuable purpose before the first VM products came along.
>EDIT: Your choice of shell can be something different than >bash... Bash is the default shell. It's also the generic command you run to launch the WSL environment. While the multiple names for the same subsystem are a little nebulous, Bash is far from being as confusing or misleading as you're attempting to portray. Also, editing your original snide grammar dismissal due to the downvotes it received isn't appreciate…
https://github.com/Microsoft/BashOnWindows/issues/846
Then, we both edited our replies. He corrected his typo, I removed my remark about the typo. At no moment there was any insult given, and the replier did not take offense.
No need for insulting.