Why does ‘false or null’ return null, but ‘true or null’ returns true?

This is all about short-circuit evaluation. In the expression 'true or null', the evaluation stops at 'true' since it doesn’t need to check any further. However, in 'false or null', it checks both sides because the left is false, resulting in null. So, the key point is that 'or' will stop evaluating once it finds a true value, hence 'true or null' gives you true.

This kind of behavior can vary between programming languages. In JavaScript, for instance, 'false || null' returns null because 'false' is falsy, so it moves on to the next value, which is null. Conversely, 'true || null' returns true because 'true' is already a valid truthy value. It’s definitely worth looking into the concepts of truthy and falsy values in your language!

You're right that null is often treated differently from boolean values across languages. Typically, 'or' operations return the first truthy value or the last one if none are truthy. In your example, 'false or null' evaluates to null because both are falsy, while 'true or null' evaluates to true since true is truthy.

Have you looked into how the 'or' operator works? Generally, if the first value is truthy, it returns that without checking the second. So with 'true or null', it returns true right away. But with 'false or null', it sees 'false', checks 'null', and ends up with null, since both are falsy just like you suspected.