SoylentNews is people
SoylentNews
Microsoft Announces PowerShell 7
Microsoft has just announced PowerShell 7, a new major release that comes only a few days after the company originally introduced version 6.2
And while it naturally makes more sense for the company to roll out PowerShell 6.3 rather than a whole new version 7.0, the company explains in a blog post that it's all as part of the efforts to align the versions of all platforms.
Steve Lee, Principal Software Engineer Manager, PowerShell, explains that Microsoft noticed a growing usage pattern on Linux, but not on Windows.
"Windows usage has not been growing as significantly, surprising given that PowerShell was popularized on the Windows platform," Lee explains. [...] The next version of PowerShell will thus be available on Windows, Linux, and macOS, and the company explains it'll be available with LTS (Long Term Servicing) and non-LTS plans.
Also at ZDNet.
Previously: MS Releases Powershell SDC - to Manage Config for.... Linux
Powershell for Linux
Your wget (and curl) is Broken and Should DIE, GitHubbers Tell Microsoft
(Score: 4, Interesting) by choose another one on Tuesday April 09 2019, @11:45AM (3 children)
This. The idea that you have to turn everything into text and then parse it back out is actually the bad idea, and the source of so many bugs and exploits, but it is so ingrained in unix that we just take the breakage as being inevitable.
I (very)vaguely recall years ago (probably before powershell) something similar was talked about for Guile (the GNU scripting lang) - I haven't kept up with Guile so don't know where it went or if that got implemented. There are GPL problems with it though (see last bit of https://www.gnu.org/licenses/gpl-faq.html#MereAggregation [gnu.org] ) - basically the whole pipeline becomes one program for GPL purposes, maybe (court will decide...).
That is pretty much Microsoft's MO.
Thing is, PowerShell's big advantage is also it's biggest drawback here - all the functions all the objects all the properties, they are the .Net ones. IF(F) you are a .Net/C# dev (or maybe VB) then PowerShell is just a bit of slightly twisted syntax to learn, then everything you usually do in C# you can do in a script, and that actually is awesome. On the other hand if you are NOT a .Net/C# dev then you have to learn not just powershell, but the entire .Net framework, for a one line script.
PowerShell is at least vaguely readable once you've written it. I used to be able to write Perl from memory, but I still had/have a library of one liners for Perl. Now, I dare not run them because I know not what they do...
(Score: 0) by Anonymous Coward on Tuesday April 09 2019, @02:52PM (2 children)
I call BS on this.
I am definitely not a .net or MS gal - Yes, Debian stole my heart of geek. I do have to admin Windows boxes. I do have to patch and maintain and support MS products inc Exchange SharePoint and Skype. You don't need to know .net to use PowerShell. It is useful to know how .net works and what's in it. For most things use the functions available and look up what you need when you need it.
I've coded in perl bash py CSH Java (yes yes) DOS batch and frankly after using PowerShell for several years I miss it when using Ubuntu or redhat. No, the Linux version of powershell is not up to scratch. Nice try though.
If not PowerShell then ... What? C#? Ask Microsoft to install python by default on all Windows machines? Install perl everywhere? Do it all in .NET?
(Score: 0) by Anonymous Coward on Wednesday April 10 2019, @07:06PM (1 child)
"I do have to admin Windows boxes. I do have to patch and maintain and support MS products inc Exchange SharePoint and Skype."
no. you don't "have to" do anything. have some self respect instead.
(Score: 0) by Anonymous Coward on Thursday April 11 2019, @11:32AM
Sure.I can starve.