Slashdot Mirror
Microsoft PowerShell Core For Linux Now Available as a Snap (betanews.com)
Canonical announced on Friday that Microsoft's PowerShell Core is now available on Linux platform as a Snap. From a report: If you aren't familiar, a Snap is essentially a packaged version of a program that can be easily installed on many Linux distributions. Many see it as the future of Linux, as it has the potential to reduce fragmentation. "Built on the .NET Framework, PowerShell is an open source task-based command-line shell and scripting language with the goal of being the ubiquitous language for managing hybrid cloud assets. It is designed specifically for system administrators and power-users to rapidly automate the administration of multiple operating systems and the processes related to the applications that run on those operating systems," says Canonical.
A piece of software that fills out a much-needed gap in the Linux world. Thanks, MIcrosoft; we could not expect any less from you.
Why, oh why, would I install something that is: .NET .NET to exist in my system in the first place?
- slow
- bloated
- in all likelihood harvesting data behind your back
- trying to replace something which isn't broken (a Linux terminal)
- dependent on
on my machine? {deity_of_choice}, why would I even permit
We all want this because...?
To experience the stability and security you've come to expect from Microsoft Windows!
Merciful heavens! A Snap containing a .NET app, just to have an inferior shell? /bin/dash is about 119K on my system.
Looks like
Traitors traditionally face a firing squad.
If he isn't hung for treason before then.
Are you off your meds?
So what is the fastest way to not install this (and DiagTra~1.exe)...?
Because the Linux way of things is so much better, where binaries from one distro won't run on another because of ever so slightly different versions between libraries or changes to ABI. Shipping binaries for Ubuntu 16.04 and don't expect them to work correctly on 14.04 or 18.04. That is how we end up in situations where teams are locked to a specific version of a specific distro.
“Common sense is not so common.” — Voltaire
I see a lot of sarcasm here... which is suprising because frankly, this is not what I have come to expect from people here.... lol
Anyways, I don't see this as something trying to replace bash or anything else, Powershell has a lot going for it, especially in the .NET world, and in particular automating work on remote machines. With emerging things like .NET Core, it seems like it would be a tremendous asset if you happened to be running something lob written in .NET, in an environment that isn't running windows.
If nothing it is designed to address doesn't apply to you, you very likely don't have a need for it. There's always SSH right? But to that end, with things like .NET core etc, I feel like shops that have always dealt with windows environments will naturally feel less intimidated with the now available linux support for server side apps, using deployment tools they're already trained in.
obligatory
You can get either for treason actually. Hence the phrase "hanged for treason"
"...designed specifically for system administrators and power-users to rapidly automate the administration of multiple operating systems..."
Oh you mean like how Windows has always treated dual-booting multiple operating systems? And support for filesystems of different operating systems? And pretty much any honest-to-goodness, not-embrace-and-extinguish support for *anything* other than M$ products on M$ operating systems, *especially* open-source products of any kind?
As I do see this as a positive move for M$, they will have precisely 30 more years of about-facing until I trust them with my Linux boxen. Until then, I hope they don't screw up.
It is pitch black. You are likely to be eaten by a grue.
If you like M$ PowerShell and want to continue to use it on Linux.. great. YAT - Yet Another Tool.
If you don't like it/don't want to use it - then DON'T!
No one is making you use it.
No one is even saying that you have to install it.
If I was working as a sysadmin (either Linus or M$) I would think it great to have the same administrative scripting system on multiple platforms. If I was a Linux only shop - meh... no reason to learn something else as Bash is working just fine.
Having used both (BASH and PowerShell) - I can say that they are both tortuous, but in different ways. They are both powerful, but in different ways. And both are products of their times.
"a packaged version of a program that can be easily installed on many Linux distributions"
So a package then?
I really NEED a Microsoft Linux distro.
Of course, with all the special Microsoft proprietary extensions.
Microsoft GNome or Microsoft KDE. And obviously a Microsoft Linux Kernel.
What dependencies could an MS package possibly have?
It's also great to have a package with dependencies all statically linked so when you update your system you still end up with software that has out of date libs with security vulnerabilities!
Can you install the VMWare cmdlets on it, or otherwise import them for use?
A *shell* as a snap seems to be an odd choice. It should be embedded in whatever environment.
Powershell doesn't make sense as an end in and of itself, and 'Snap' and similar strategies only really possibly make sense for software that is an end in and of itself...
XML is like violence. If it doesn't solve the problem, use more.
break the monopoly on gaming, M$, release DirectX for the world as FOSS. fund and promote OpenGL. anything less is just a camel nose under the tent of *nix as a way to gain power and EEE.
Comment removed based on user account deletion
Instead of you do automate it ...
It automates you!!!
MS PowerShell fanbois aren't going to use Linux and us old crusty Linux/Unix admins don't want to use PowerShell.
I installed this Wednesday to check out a challenge someone posted in a forum.
The challenge was to implement the following powershell script using bash:
param(
[Parameter(Mandatory=$True)]
[datetime]$FromDate,
[Parameter(Mandatory=$True)]
[datetime]$ToDate,
[Parameter(Mandatory=$False)]
[ValidateScript({Test-Path -PathType Container $_ })]
[string]$Directory = '.'
)
Get-ChildItem -Include '*.JPG','*.PNG' -Recurse -Path $Directory | Where-Object { $_.CreationTimeUtc -ge $FromDate -and $_.CreationTimeUtc -le $ToDate } | ForEach-Object { $_.FullName }
The challenge author also specified that the bash script should match the functionality of the above including:
Code:
Get-Help
test.ps1 [-FromDate] [-ToDate] [[-Directory] ] []
My first thought was, "I can get a bash script to run on any version of Windows and have been happily using bash and tcsh on Windows since Windows 95 in the 90s. Can that Powershell script run on Linux?" Surprisingly, I installed the powershell core snap, copied the script to test.ps1, and ran it with no issues. It doesn't convert me to powershell, but I was surprised the argument didn't hold.
Snap ... Many see it as the future of Linux, ...
And many don't. (but they did, back in the 1980s when static-linking was all the rage)
PowerShell ... is designed specifically for system administrators and power-users to rapidly automate the administration of multiple operating systems ...
Meaning: Windows, Windows Server ...
It must have been something you assimilated. . . .
To elaborate on that last point: being dependent on works under the "Microsoft Patent Promise for .NET Libraries and Runtime Components" is considerably dangerous because of the profound limits for software reuse and modification, and because of how limited this "patent promise" is. You cannot deal in the "Microsoft Patent Promise for .NET Libraries and Runtime Components" covered software as you can with free software (which is so named because it respects a user's freedoms to run, inspect, share, and modify the software) under, say, the GNU General Public License version 3 (GPLv3). Here are a few highlights from that article:
That's a huge danger, particularly to anyone used to working in free software where merging code between compatibly-licensed programs is the norm. Your interests as a user (regardless of your technical skill or willingness to learn technical skills) is far better served by the GPLv3 (also covered at the aforementioned article). The GPLv3 is simply far more straightforward and clear about your permissions, and the GPLv3 grants you what you need to deal fully in the software respecting your software freedom the whole time.
Digital Citizen
Powers hell.
IME it's a powerful but clunky piece of garbage.
My ism, it's full of beliefs.
I already have a fucking shell that works great. Why would I ever use your fucking garbage?
Clearly all of the comments I cared to read are poor souls stuck in the 2000s. Really, VMware, and multi-os shops, are the reasons people like this shit. There are so many jobs for cloud native apps you suckers just need to polish your resumes and get a pure Linux job. This shit is hilarious, and serves no purpose other than for Microsoft to try to stay relevant.
So two evil companies released one shitty product packaged in another shitty product?
No thanks.
... is about the dumbest fucking thing I have ever read.
Clickety Click
Every .Net application I have tried has resulted in core dumps and crashes which were so frequent the apps were uninstalled. Once a day is too much and twice a week is enough to get on my nerves. No doubt this one will be a winner though. Ya right.
"Embrace, Extend.... uuuuh
uhhh....
er.... .... EXTINGUISH!
Those who fail to study the lessons of history... ...are doomed to make it up in summer school.
EEE. They want to make Windows a Linux distro
No, MS wants to make Linux a Windows Distro, FTFY
you get like 11 different copies of the same library
Which isn't really a problem if you're using a deduplicating filesystem.
Paramount.