use of '||' and '&&'
Looks like that it took nearly 2 decades to make it do what C was doing in the 70's... and what the POSIX shell was doing in the 80's!!!
POSIX shell syntax with operators and return codes can seem a bit complex at first. But it should work like the C language rules for '&&' and '||' and then it makes sense. For consistency, Power Shell needs to duplicate that [and not try to set the trend on its own]. If I read things correctly, it's going to do that now?
/me points out that MS "setting the standard" has pretty much backfired in the much wider world outside of Windows. It's "/" not "\" for path names, EXCEPT WINDOWS and DOS. It's POSIX shell-like substitution for parameters and environment everywhere *EXCEPT* windows and DOS. The use of PATH and other environment variables is standard EXCEPT for Windows [which uses the registry for 'ShellExecuteEx']. And so on.
And that whole ".Not" thing is its OWN nightmare. I don't EVEN want to begin with *THAT*.