const value = cond ? a : b;
Using an if instead would mean you can't make it const, and is usually more convoluted to read.For pretty much all other use cases, I agree that ifs are better.
For example, the following F# code (you can run `dotnet fsi` in a terminal to try it out, if you have dotnet installed) is equivalent to a ternary expression:
// the value of x is "is_not_lower" after evaluation (x is a constant/immutable value, just like a 'const' value in JS) let x = if 0 > 1 then "is_lower" else "is_not_lower"
Which is equivalent to the following (in JS): const x = 0 > 1 ? "is_lower" : "is_not_lower"
In F# (and also Kotlin which I linked before), you can have clean code with if-elif-else ladders while the equivalent (using nested ternaries) would be hard to read. For example:
// the constant/immutable variable "comparison" is either "HIGHER", "LOWER" or "EQUAL" depending on the branch taken let comparison = if a > b then "HIGHER" elif a < b then "LOWER" else "EQUAL"
In JS land (and also most common programming languages which have plain if-statements), I agree a ternary would often be preferrable as long as it's not nested.
a = if x then y else z
is just a more verbose version of a = x ? y : z;
Raku uses yet another form of the same operator: a = x ?? y :: z;
Syntactic sugar :-) a = x ?? y !! z
And that's because a single : is used for many other semantics in the Raku Programming Language. And ?? and !! standout better in code.I think I made this mistake because :: was used in one of the drafts for Perl 6, but the final specification uses !!
a = (x < 5 ) ? 'LESS'
: (x > 5 ) ? 'MORE'
: 'SAME';