Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Command Line and Windows Subsystem for Linux – The Windows 10 April Update

anandtech.com

Post reply on HN
Print view View original

61–70 of 80 posts

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#61

Post by guilhas »

frankohn wrote: post #8

I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…

Agreed. I was watching a channel9 video on vscode and OSS, their contempt for the rest of OSS community was visible.

The marketing changed, but the "open source is inferior" culture is still there.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#62

Post by willtim »

ktpsns wrote: post #59

> [...] to start an argument, case sensitivity is one of the most annoying features of Linux. This is of course so much opinion-based, but my feeling is that in absolute numbers, machines which distinguish between upper and lowercase in file names surpass machines which don't. At least since the global market is dominated by Unix-inspired operating systems (iOS, Android) in the end ;-)

Not to mention, that case-insensitivity requires knowledge of locale/encodings and all the associated complexity. Not every language even has the concept of case.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#63

Post by guilhas »

ta848347 wrote: post #30
frankohn wrote: post #8

I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…

> They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc This is ridiculous. Damned if you have a CLI, damned if you don't. Further more, if Microsoft where to extend it, wouldn't it need to contribute back to the community? Isn't Microsoft one of the leading if not biggest contributors to opensource on…

And yet we could live without all their github open source contributions.

They haven't really created anything new, so not leading, they just go after the community and release what they can't keep closed. Or create their flavor of other existing OSS. Although their R&D is great.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#64

Post by [deleted] »

pritambaral wrote: post #44
oblio wrote: post #37

Earlier quoted context omitted.

I’ve been using Linux for more than 10 years. Don’t be ridiculous. Linux desktop usage has always been pitiful, 2% of the market at best. What is there to extinguish? There is a reason “the year of Linux on the desktop” is a meme. You’re completely misreading their strategy. They’re targeting development for Azure. These days a ton of development tools are *nix native and Windows is a second class citizen, because Li…

> What is there to extinguish? The Linux CLI development environment? The point of WSL clearly can't be to try to extinguish the Linux Desktop , because WSL doesn't even embrace the Linux Desktop.

[deleted]

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#65

Post by dugmartin »

megaman22 wrote: post #20
pbowyer wrote: post #16

Earlier quoted context omitted.

> It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it. I find Git fine, but the Vagrant/Virtualbox ecosystem... I dread every Windows update because something will break the setup, and that will be a day lost to figuring out which version of every component I need in order for my Virtual Machines to boot/build. I would pay money for somethin…

Run VMs in Hyper-V. That just works

My vagrant install failed under HyperV after the update. After spending a couple of hours trying to get it working again I switched over to Docker for some legacy Rails projects and installed native binaries for the Elixir project I was working on. I’ve used Vagrant for years but I guess it was time to move on.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#66

Post by mark_l_watson »

thom wrote: post #58
frankohn wrote: post #8

I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…

I honestly think this is more of a reaction to Macs having had a perfectly good POSIX environment for ages, resulting in the Apple ecosystem grabbing a lot of developer mindshare (or at the very least developer dollars). I don't think it's at all surprising that you can't create Windows apps that run within WSL, because I don't think Microsoft see this as Windows as a desktop interface to Linux. I think they just see…

I think it is a response to macOS and trying to make it easier for developers to use Azure.

Sorry, a bit off topic, but I would like to talk with someone who has compared dev on macOS, Windows with Linux support, and the new Google ChomeOS Linux sandbox. I am tempted by the latter, but I would like to hear from many more people who have tried it.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#67

Post by nickjj »

One cool thing about the update is WSL's filesystem now supports metadata which can store Linux file permissions.

So instead of having 777 permissions everywhere you can have your WSL mounted files and folders have correct permissions.

Problem is popular code editors like VSCode will strip this metadata every time you save a file.

If you want to see this fixed, please post about the issue in https://github.com/Microsoft/vscode/issues/49021.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#68

Post by nickjj »

JonasJSchreiber wrote: post #11

I really wish that Docker could natively run in WSL. It's a really aspirational project for Microsoft, but it's not doing anything that Cygwin doesn't at this time.

It doesn't run natively but it's really easy to interact with Docker from WSL.

You can follow the steps to set this up at https://nickjanetakis.com/blog/setting-up-docker-for-windows....

I use it every day and it's great.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#69

Post by zmix »

hirsin wrote: post #38
zmix wrote: post #23

Wouldn't it have been better for Microsoft to support https://midipix.org , which would have resulted in more finegrained POSIX support for Windows, rather than installing an isolated machine, that runs seperate?

What isolated machine? Open up WSL, run "CMD.exe notepad", then top. You'll see the instance of notepad running, and then you can go kill it with taskmanager. People still seem to think it's a VM when it's not - the pid in the Linux system is the same pid in Windows, it just hits a different part of the kernel.

You are right, I was assuming, it'd be running in a VM. At least, that was what was being said, when this project got introduced to me a while ago.

I still don't sympathize and would prefer Microsoft putting other efforts, than this, into making Windows more POSIX aware/compatible.

Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update

#70

Post by harrygeez »

tybit wrote: post #33
frankohn wrote: post #8

I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…

Why would they want to embrace, extend and extinguish Linux when nowadays the competition is no longer Linux but AWS, Google etc?

This. So much this.
Post reply on HN