stop - When you see (condition === true) T_T :') - devRant

Ranter

Comments

8

Seethe

459

9y

=== is not == there may be a good reason for this.
5

Theo20185

541

9y

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#.
1

W1ckeD

732

9y

@Theo20185 Jezus Christ. Did you survive?
0

Theo20185

541

9y

@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.
1

shittywebdev

5359

9y

@Theo20185 So if code smell is a thing, was that lead smell?
5

luciam91

37

9y

Am 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...
0

bkrem

1272

9y

@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.
1

naitsabes

250

9y

@Theo20185 ick

Related Rants

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service