I sort of expect to be able to compare to true. So I code a switch node with "==" and look for a boolean type that I can set to true. I don't find one, so I reluctantly match with the string "true". My fairly complex flow doesn't work properly and it takes me wwaaaaayyyy too long to realise that boolean true != string true (I blame the red wine). So I Google it, and then realise "is true" and "is false" exist on the switch node. Doh! But really? How many people are going to encounter the same 'problem'? Surely most languages these days would coerce a boolean to a string and it would work.
Even better, all of this could be solved by leaving "is true" but also allow a boolean type in the comparison. I know I'm going to make the same mistake again and again. Please! Thoughts?
EDIT... And to fix up my potential mistakes in other nodes, why does searching (ctrl-F) for "true" seem to match with "on"?