But you aren’t using Windows.
You’re also now adding a .NET Core requirement for any Linux box wanting to use it.
That means limited functionality as its not the full blown .NET framework.
So, compared to something like bash, you now have added requirements with less functionality.
To answer your original question though, a lot of people prefer zsh as its got a crazy amount of customization you can do.
People also like fish due to it being very friendly and interactive.
limited functionality as it’s not the full blown .NET
This is misleading to the point of being completely wrong
On Linux, you do not have access to Windows UI frameworks like WinForms, the Windows registry, and to System.Drawimg (because it is just a thin wrapper over Win32). Essentially the entire .NET standard library is available on Linux.
I would argue that .NET is actually better on Linux for some things (like web dev).
That said, I can see no reason to use PowerShell on Linux unless you are a .NET dev.
There are PowerShell cmdlets that do not work on Linux. Again, mostly stuff that talks to explicitly Windows services and sub-systems. But that has nothing to do with .NET at all. Also, path separators and case sensitivity is different on Linux. So, cross-platform scripting is a pain.
I’ve once created a profile with about 1500 lines of code for powershell, managing AD at work. It was great to learn, it’s great for scripting and it’s very intuitive (for me at least), I also liked working with objects.
I wouldn’t use it on Linux though, I’m not sure how well integrated it is.
I’m using fish at the moment, desktop and server, and I like it primarily for the functions and the autocomplete
Why not? It seems like a well supported shell on windows that isn’t terrible.
But you aren’t using Windows. You’re also now adding a .NET Core requirement for any Linux box wanting to use it. That means limited functionality as its not the full blown .NET framework. So, compared to something like bash, you now have added requirements with less functionality.
To answer your original question though, a lot of people prefer zsh as its got a crazy amount of customization you can do. People also like fish due to it being very friendly and interactive.
This is misleading to the point of being completely wrong
On Linux, you do not have access to Windows UI frameworks like WinForms, the Windows registry, and to System.Drawimg (because it is just a thin wrapper over Win32). Essentially the entire .NET standard library is available on Linux.
I would argue that .NET is actually better on Linux for some things (like web dev).
That said, I can see no reason to use PowerShell on Linux unless you are a .NET dev.
There are PowerShell cmdlets that do not work on Linux. Again, mostly stuff that talks to explicitly Windows services and sub-systems. But that has nothing to do with .NET at all. Also, path separators and case sensitivity is different on Linux. So, cross-platform scripting is a pain.
I’ve once created a profile with about 1500 lines of code for powershell, managing AD at work. It was great to learn, it’s great for scripting and it’s very intuitive (for me at least), I also liked working with objects.
I wouldn’t use it on Linux though, I’m not sure how well integrated it is.
I’m using fish at the moment, desktop and server, and I like it primarily for the functions and the autocomplete
bash is also well supported in Windows via WSL