Finally! PowerShell Remoting just plain sucks, at least it has for me. I've always wondered why the PowerShell developer(s?) would do something so needlessly contrived when SSH has been around for, like, twenty years or so.
This will definitely make my job easier! Or at least more convenient.
"I've always wondered why the PowerShell developers ..." Think about the beginning of that sentence. They invented a new console language, when bash has been around forever and C# is a better programming language generally and can be run as a scripted language with a little finagling.
I don't think the PS team is bad (or PS itself for that matter), I just think there was a lot of re-inventing of the wheel for no reason, and that started way upstream of remoting.
They didn't reinvent the wheel. Bash was intended for a Unix environment with all the corresponding utilities.
PowerShell was designed for a Windows/.NET environment, which is undeniably different, and they also took the opportunity to create an object oriented shell instead of a text oriented one.
I also like C# but I do feel it makes a pretty poor scripting/shell language.
I do think SSH is long overdue, but based on the post it looks like the developers have always been on the right track - management just wouldn't let them do it. Really glad this is changing.
I hope people don't actually believe PowerShell is NIH.
PowerShell had good reasons to exist in 2006, when it was released to the public. LINQ didn't exist yet, most of the "Windows scripting" took place via VBScript files and WMI, and dinosaurs roamed the earth.
So PowerShell was created to be a "scripting language for Windows".
PowerShell has a lot of great features specifically created for use in the shell, and some ok features (like easy COM integration) that were great in 2006. If you don't know what those are, I guess you could draw the conclusion that it's just another .NET language.
The object-pipeline system was a real, important innovation. Bourne shell has a number of known deficiencies, especially as soon as your filenames have spaces in them. I think those were reasonable reasons.
PS remoting and PS security restrictions on script files are the wheels that have been reinvented square.
Well, either way, I'm glad they have finally decided to go for SSH.
I'm still not sure I really like PowerShell, but whether one likes it or not, it has become too useful to ignore. And even on days when I really dislike it, it is still a huge improvement on cmd and vbs. I still do a lot of my Windows scripting in Perl, mostly because I am familiar with it, CPAN still rules, and I am not sure I want to learn the .Net framework just so I can do some admin-type scripting. But it's good to have options.
This will definitely make my job easier! Or at least more convenient.