Shell Speeds, Bash and PowerShell
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Now there's a circle if I ever seen one. PowerShell on Linux to manage Linux apps through an API that can only be managed by PowerShell?
Where is the circle? A shell to manage an app that can only be managed that way... sounds like any app, really.
It might sound like a circle if we get the false sense that PS is a Windows tool and not just a shell. But it is just a shell and works on Linux just like anywhere else and is, sadly, the sole management platform supported by some SaaS apps. But there is no circle at all, just dumb apps that only interface with one shell. But Windows isn't involved in any way, and PS on Linux would be the ideal solution.
What doesn't use Rest API? Sounds like a horrible service and app.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Why did you want PowerShell on Linux? For better remote Windows management?
Since it doesn't do that, that wouldn't make any sense. We wanted it for app management of apps that use APIs only available in PS, but not for Windows management in any way. Obviously, we want Bash for Windows management, it works better.
I was thinking more along the lines of running a PowerShell script. You have to choose a server to run it on. I'd rather run it for free on Linux, rather than pay for a Windows Server license.
But you can run that in Bash, Python, etc all better than PS. Ps offers no advantages.
Of course if you WRITE the script in PS, it has to run in PS. But you'd not write it if you aren't using it. And the script that does the work has to run on the Windows box, not Linux, so just use Bash for a better experience.
Not if the PowerShell script interacts with things BASH does not interact with as well or efficiently as, or not at all with.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
What doesn't use Rest API? Sounds like a horrible service and app.
Most things don't use a Rest API. Rest is nice, but most stuff doesn't use that. That's extremely modern and if you work with MS products, you rarely get things that are modern or well designed. Hence this entire discussion of a shell that should never have existed at all, and yet it does. Same principle.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Not if the PowerShell script interacts with things BASH does not interact with as well or efficiently as, or not at all with.
Example? I get this in concept, but I'm not aware of anything that falls into this category. AFAIK Bash does this better or equally in all scenarios.
-
I used PowerShell today and it was awesome.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
I used PowerShell today and it was awesome.
It actually works better on Linux than on Windows. Launches faster, and integrates quite well. If you like PS, it actually is 100% functional on Linux. And that's PS6, not the old version that Windows ships.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
I used PowerShell today and it was awesome.
It actually works better on Linux than on Windows. Launches faster, and integrates quite well. If you like PS, it actually is 100% functional on Linux. And that's PS6, not the old version that Windows ships.
Yeah 6 is great. That's what I use unless I need a specific Windows module.
-
Just wait until .NET Core 3 and PS7! You will see the light.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
I used PowerShell today and it was awesome.
It actually works better on Linux than on Windows. Launches faster, and integrates quite well. If you like PS, it actually is 100% functional on Linux. And that's PS6, not the old version that Windows ships.
Yeah 6 is great. That's what I use unless I need a specific Windows module.
Unfortunately we need those specific modules for SO many tasks that we do every day. Otherwise we'd happily use PS6 Core on Linux.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Just wait until .NET Core 3 and PS7! You will see the light.
What's new in 7 of interest?
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Just wait until .NET Core 3 and PS7! You will see the light.
What's new in 7 of interest?
https://redmondmag.com/articles/2019/04/05/powershell-7-coming.aspx?m=1
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Just wait until .NET Core 3 and PS7! You will see the light.
What's new in 7 of interest?
https://redmondmag.com/articles/2019/04/05/powershell-7-coming.aspx?m=1
Sounds like basically nothing. Striving for 90% compatibility, but that's a far cry from "able to replace." Other than cleaning up some branding and normal invisible updates, nothing of note coming as you'll still be running PS and PSC side by side with PSC indefinitely "not ready yet" to take over
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Just wait until .NET Core 3 and PS7! You will see the light.
What's new in 7 of interest?
https://redmondmag.com/articles/2019/04/05/powershell-7-coming.aspx?m=1
Sounds like basically nothing. Striving for 90% compatibility, but that's a far cry from "able to replace." Other than cleaning up some branding and normal invisible updates, nothing of note coming as you'll still be running PS and PSC side by side with PSC indefinitely "not ready yet" to take over
Getting better, exciting changes! I'm looking forward to everything. It's all good stuff IMO.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Just wait until .NET Core 3 and PS7! You will see the light.
What's new in 7 of interest?
https://redmondmag.com/articles/2019/04/05/powershell-7-coming.aspx?m=1
Sounds like basically nothing. Striving for 90% compatibility, but that's a far cry from "able to replace." Other than cleaning up some branding and normal invisible updates, nothing of note coming as you'll still be running PS and PSC side by side with PSC indefinitely "not ready yet" to take over
Getting better, exciting changes! I'm looking forward to everything. It's all good stuff IMO.
Better, yes. Just seems to move like molasses. Such tiny changes, they have a gap to breach and they need to just bite the bullet and do it.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@Obsolesce said in Shell Speeds, Bash and PowerShell:
Just wait until .NET Core 3 and PS7! You will see the light.
What's new in 7 of interest?
https://redmondmag.com/articles/2019/04/05/powershell-7-coming.aspx?m=1
Sounds like basically nothing. Striving for 90% compatibility, but that's a far cry from "able to replace." Other than cleaning up some branding and normal invisible updates, nothing of note coming as you'll still be running PS and PSC side by side with PSC indefinitely "not ready yet" to take over
Getting better, exciting changes! I'm looking forward to everything. It's all good stuff IMO.
Better, yes. Just seems to move like molasses. Such tiny changes, they have a gap to breach and they need to just bite the bullet and do it.
I wouldn't call them tiny, it also depends on .NET Core 7.
It's still moving faster than some software
-
I skipped the discussion, but I see two main points here:
- Plenty of DSLs support both Windows and Linux, they are made for automation, use them.
- For anything more complex, where you actually have to script and a DSL gets too clunky, bash/powershell also tend to get too clunky and hacky to be useful. I simply revert to Python - it runs on both platforms and is much more powerful than either bash or powershell.
-
@dyasny said in Shell Speeds, Bash and PowerShell:
bash/powershell also tend to get too clunky and hacky to be useful. I simply revert to Python - it runs on both platforms and is much more powerful than either bash or powershell.
Absolutely, I never use BASH for any serious automation. Nor PowerShell. Neither is a good tool once you go beyond "shell" functionality.
-
@scottalanmiller said in Shell Speeds, Bash and PowerShell:
@dyasny said in Shell Speeds, Bash and PowerShell:
bash/powershell also tend to get too clunky and hacky to be useful. I simply revert to Python - it runs on both platforms and is much more powerful than either bash or powershell.
Absolutely, I never use BASH for any serious automation. Nor PowerShell. Neither is a good tool once you go beyond "shell" functionality.
What's beyond shell functionality? I don't think I've come to that point or had a need to?
-
I think if rather use node for things past Bash or powershell. By design I think it would be a better performer than Python.
-
@Obsolesce said in Shell Speeds, Bash and PowerShell:
What's beyond shell functionality? I don't think I've come to that point or had a need to?
Once you are writing anything extensive. Long scripts where you'd want to move past vi and whipping it up in an hour or two. Once you move from "quick couple things strung together" to "writing software to manage automation".
The ability to be a good shell basically guarantees you can't be good at automation. BASH and PS are both good examples of this. They try to do too much, and it encourages people to use them for too much. PS especially.
