But given the choice, and considering the impending explosion of PowerShell based malware, I’ll still stick to *nix and native shells there. Yes PowerShell in general is pretty good if you are running Windows.

Nuget if you(the reader) don’t know is the package manager for MS’s developer tools and do you really want that on a potentially production server?! That to me just screams one more way for a Windows server to be hacked. You fail to mention the need for installation of and access for additional tools like nuget which is required with these steps. Lindows/Winux may actually be something that I’d consider from MS.īack to the original item here of the article. IF MS wants to do something good, create a gui for Linux or pull an apple, dump your core and port your ui to Linux. In the end, you are still stuck with the inherent limitations of Windows for this lipstick on a pig. In fact, if an app does run, it’s largely because their required libraries were ported to Windows as well. Lots of hype here.Įven Jack Hammons at MS has written that this subsystem was geared towards bash and cmd line tools and that it doesn’t even support any desktops or apps. In fact most apps will not run in this as there is still a substantial difference for how a true Linux OS performs compared to what this truly offers. The implementation is still limited for both commands and apps. Eventually it’s going to fall because the cliff is unstable. Linux subsystem on Windows so that you can run Linux commands and programs on Windows.

Filezilla ssh windows 10