Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I had a lead once that insisted the project style would include == true or == false for all conditionals. The ! operator was not allowed. At least we were allowed to use && and ||. Language was C#.
-
@W1ckeD Yes, I just let it roll off. The code was functionally unchanged. This was not something I was going to pick a fight over.
-
luciam91378yAm I the only one who doesn't see an issue with this? Unless I'm missing something I'd always recommend using triple-equals where possible...
-
bkrem12738y@luciam91 it's redundant in terms of syntax, in JS you could simply do `if (condition)`.
But semantically there is an (IMO weak) argument for making the boolean comparison explicit.
Related Rants
When you see (condition === true) T_T :')
undefined
stop
condition
frustrating
funny