Re:PowerShell Remoting
by 13of40 on Tuesday August 21, 2018 @08:36PM
(#17815164)
One benefit you get with powershell to powershell remoting is that the output of the commands come back as objects rather than text. You can even use "implicit remoting" (not sure if that's the marketing term) to make the remoting part of it transparent to your automation - see Import-PSSession.
[ Parent
| on HN ]
Re:PowerShell Remoting
by reificator on Tuesday August 21, 2018 @08:39PM
(#17815185)
That's a pretty cool feature, but I don't often remote into machines and then want to do the processing locally. Maybe that's because I don't have this feature, but I've never felt like I wanted to. Usually I just treat the client like a dumb terminal.
I'd bet a project like Ansible could use something like that to great effect though.
IIRC, the main scenario for implicit remoting was where you were exposing a management interface for a service in no-language mode (i.e. the server will only run a whitelisted set of commands and no other scripting, for security) and any complex scripting needs to be done client side. So you'd open a console, import the commands from the remote machine, and now you can interact with it to do things scoped to your role, like diagnostics or restarting a service, etc.
Re:PowerShell Remoting
by reificator on Tuesday August 21, 2018 @08:59PM
(#17815313)
That makes sense...
Its pretty cool actually, called Just Enough Administration, and its well supported.
From what I understand, PowerShell has been open-sourced and ported to Linux. Are non-Windows users adopting it? It's probably facing a long climb. Having 30+ years of productivity hacks is tough to compete with.
Re:PowerShell Remoting
by reificator on Tuesday August 21, 2018 @08:58PM
(#17815307)
Part of it has, yeah. Personally I use it fairly frequently for scripting tasks on Windows, but have yet to have the urge to install it on anything else.
Re:PowerShell Remoting
by 3rdAccount on Tuesday August 21, 2018 @09:25PM
(#17815465)
I use PowerShell on Windows because CMD is atrocious and some things just aren't great in Windows for Python. C# is also not efficient for those people used to the efficiency that comes with a Linux terminal and how to use it.
When I'm on Linux, I have tons of commands, bash, python, perl, Awk, sed...etc etc. All of those tools work perfectly with text which the Unix style OS embraces. Windows on the other hand is all objects and this can be painful in PowerShell at times.
Tldr; PowerShell is alright on Windows as it is the only real viable option for a power user. However, Linux is far better with what it already has and PowerShell would be a step backwards in functionality and efficiency.
WSL (Windows Subsystem for Linux) is doing a pretty great job of making those *nix commands easily available on Windows. I don't know if it's ready for say DevOps day-to-day professional usage, but just being able to find, grep, awk on Windows works great for me.
Re:PowerShell Remoting
by 3rdAccount on Thursday August 23, 2018 @06:37AM
(#17826076)
Sadly I'm still on Windows7. I'll start the fight with IT over access (I assume configuring it requires admin) as soon as I'm on Windows10.
It's interesting - I get to a certain point with Powershell and then jump into Visual Studio to accomplish whatever I'm trying to do in C# instead.
I think it'd be better if there was a fully supported way to debug Powershell inside Visual Studio - the IDE is a step backwards.
Imagine if Microsoft focused on IronPython and added a high level of integration with PowerShell and/or Python-extensible utilities. Running/executing PowerShell from within a Python REPL would really be something.
Re:PowerShell Remoting
by cryptonector on Wednesday August 22, 2018 @01:11AM
(#17816468)
OTOH there is no online streaming, right?