SoylentNews is people
SoylentNews
Some exceedingly odd news today from the world of Microsoft:
Today's customers live in a multi-platform, multi-cloud, multi-OS world – that's just reality. This world brings new challenges and customers need tools to make everything work together. Microsoft is working company-wide to deliver management tools that empower customers to manage any platform, from anywhere, on any device, using Linux or Windows. This shift to a more open, customer-obsessed approach to deliver innovation is one of the things that makes me most excited to come to work every day.
You've heard Satya Nadella say "Microsoft loves Linux" and that's never been more true than now. Nearly one in three VMs on Azure are Linux. Nearly 60 percent of third-party IaaS offers in the Azure Marketplace are open source software (OSS). We have forged strong industry partners to extend choice to our customers. We've announced SQL Server on Linux, as well as open sourced .NET. We added Bash to Windows 10 to make it a great platform for developing OSS. And, we're active contributors and participants to numerous open source projects (e.g. OpenSSH, FreeBSD, Mesos, Docker, Linux and many more) across the industry.
Today, we are taking the next step in our journey. I am extremely excited to share that PowerShell is open sourced and available on Linux. (For those of you who need a refresher, PowerShell is a task-based command-line shell and scripting language built on the .NET Framework to help IT professionals control and automate the administration of the Windows, and now Linux, operating systems and the applications that run on them.) I'm going to share a bit more about our journey getting here, and will tell you how Microsoft Operations Management Suite can enhance the PowerShell experience.
I have no words. Well, I do but they're mostly of the four-letter variety and in random order.
(Score: 3, Interesting) by number6 on Friday August 19 2016, @01:53PM
The author of 'curl' (Daniel Stenberg) has requested Microsoft to remove all aliases to 'curl' inside PowerShell.
Here is the pull request at GitHub [github.com]
Here is his blog post on this [daniel.haxx.se]
(Score: 4, Insightful) by Bot on Friday August 19 2016, @02:13PM
Account abandoned.
(Score: 2) by RamiK on Friday August 19 2016, @02:30PM
Please. We had namespace wars in Unix since the BSD vs. GNU sed \ awk flags wars. To this day, you have people complaining about bash stealing cd and ls aliasing...
It's why sane distros use busybox in their initramfs. Not the size. That doesn't matter in x86. But because they don't want to delve into the politics.
compiling...
(Score: 0) by Anonymous Coward on Saturday August 20 2016, @04:41AM
It's not a namespace problem though. Powershell has a feature called "aliases" which allow you to wrap commands around a shorter syntax. The problem with this is that the Powershell team, in all their wisdom, decided to simply wrap a number of Unix commands to "aliases", probably so they could be cool or something, or just to help some seasoned CLI users with quick commands ("ls" invokes "dir", while "curl" invokes "Invoke-WebRequest).
The problem is it shits on itself once they open-source it. Or when any sane user chooses to install curl.
What they should've done is provide these semantics as a default in the profile.ps1 configurations they have for users. That way, it kills two problems quickly: namely where do you find the customizable shell script for your user (profile.ps1 isn't created by default) and 2) this issue when users try to install more sane tools than the ones provided by Windows.
(Score: 0) by Anonymous Coward on Saturday August 20 2016, @10:05PM
I guess the awk flags are correctly documented in manpages, for each implementation, and people are going to look there when something breaks. Aliases are quite easy to edit without having to fork. This is different, if you want a linux equivalent you gotta look for that very controversial piece of software who took over PID 1 whose creators are allergic to being BASHed for obvious reasons.