Hmm... If that's the case, that's news to me. I'll admit I don't do much with Fedora, I'll have to take a closer look at them.

Fedora is not rolling at all, it just has a fast release cycle

I mean, that's definitely a downside to long term stable distros. So, basically, the choice is between that and a rolling release which has the downside of the possibility of things breaking on update and never really having an easily reproducible build

It is not randomly frozen as Mint does follow Ubuntu's LTS releases, every new version they put out is based on whatever the current Ubuntu LTS is. Their release cadence isn't linked that closely as a new LTS usually takes a few months to spawn a new Mint release based on it, but they aren't just freezing some arbitrary point in time of development.

If you mean Ubuntu is randomly frozen, it isn't either. It follows a release schedule, determines a roadmap, and at a certain predetermined point in developing a new release, they do freeze for new versions so they can complete testing and ensure everything works together in time to release on schedule. It's certainly not "random".

And that's also not what stability means. Stability means functionality doesn't change, so an up to date Mint 21.3 installed on release is going to be the same as one installed and updated now, functionally speaking. This is accomplished by only backporting important security patches and bug fixes to the version of the software that's used by the system rather than getting it with new versions where there are new features and changes to existing functionality that can break things based on the previous version. This does not mean it gets all fixes, just the ones they deem worth the effort of backporting.

But it's not randomly frozen, it's tied to Ubuntu's LTS builds. And they didn't say "stable" is the same as "works well", they said Mint is both (which is true from my experience at least)

If you need newer packages with Mint, Flatpak is a good way to go (yes it has its own issues, but they do work well for a lot of people)

Does that make it better?

Not sure what's extravagant about it... Fully object oriented pipeline in a scripting language built on and with access to the .NET type class system is insanely powerful. Having to manipulate and parse string output to extract data from command results in other shells just feels very cumbersome and antiquated, and relies on the text output to remain consistent to not break

PowerShell, it doesn't matter if more or less data is returned, as long as the properties you're using stay the same your script will not break

Filtering is super easy

The Verb-Noun cmdlet naming convention gets a lot of (undeserved) hate, but it makes command discovery way easier. Especially when you learn that there's a list of approved verbs with defined meanings, and cmdlets with matching nouns tend to work together.

It actually follows the Unix philosophy of each cmdlet doing one thing (though sometimes a cmdlet winds up getting overloaded, but more often than not that's a community or privately written cmdlet)

It's easily powerful enough to write programs with (and I have)

And it works well with C#, and if you know some C#, PowerShell's eccentricities start to make way more sense

Also, I mainly manage Windows servers for work running in an AD domain, so it's absolutely the language of choice for that, but I've been using it for probably close to 14 years now and I can basically write it as easily as English at this point

Yeah, PowerShell does do things that don't exactly make sense without having some understanding of the underlying dotnet and what the components actually do

I'll probably give it a spin anyway, might be I find some benefit and it looks like an interesting project. Being Rust based instead of C# .NET based could theoretically make it a lot faster (though I've not really had an issue of speed in PowerShell)

V1 never actually shipped with any version of Windows

Windows 7 shipped with V2, 8 with V3, 8.1 with v4, and 10 with v5 and later 5.1.

5.1 is the latest (and last) version of Windows PowerShell.

All versions after that are just PowerShell (or PowerShell Core for version 6)

Not sure why they don't bundle it by default, but starting at v7.2 it can be updated by Windows update

Just looking at it briefly it looks a lot like PowerShell, any reason to use it over PowerShell?

PowerShell, with zsh being a close second