Question

The constructs -ne, -eq, and -gt looks at least strange.

if ($true -eq $true){}

but not

if ($true = $true){}

What is the explanation?

Answer 1

Basically the answer is that it is how Unix has done it forever. Sure enough, if you write some Bash scripts that’s what you’ll use and it’s actually nice to have your PowerShell syntax knowledge transfer over one for one to Bash.

It is answered in detail in Bruce Payette’s Windows PowerShell in Action, Second Edition (Kindle Location 3391).

Let’s talk about the most contentious design decision in the
PowerShell language.

And the winner is: why the heck didn’t we use the conventional symbols for comparison like >, >=, <, <=, ==, and !=?

The answer is that the > and < characters are used for output redirection. Because
PowerShell is a shell and all shell languages in the last 30 years
have used > and < for I/O redirection, people expected that PowerShell
should do the same. During the first public beta of PowerShell, this
topic generated discussions that went on for months.

We looked at a
variety of alternatives, such as modal parsing where sometimes > meant
greater-than and sometimes it meant redirection. We looked at
alternative character sequences for the operators like :> or ->,
either for redirection or comparison. We did usability tests and held
focus groups, and in the end, settled on what we had started with.

The redirection operators are > and <, and the comparison operators are
taken from the Unix test(1) command. We expect that, because these
operators have a 30-year pedigree, they’re adequate and appropriate to
use in PowerShell. (We also expect that people will continue to
complain about this decision, though hopefully not for 30 more years.)